DapperReleaseSchedule

  • Please do not edit

  • Freezes normally happen at the start of the given date, UTC time. So last minute changes need to happen the day before.
  • The rationale for this schedule is captured at DapperReleaseProcess

  • NOTE: this schedule has been revised to delay the final release by 6 weeks, with corresponding changes to various other deadlines (MattZimmerman, 2006-03-16)

  • See DeveloperResources for the freeze exception process.

Week

Date

Task

Status

Notes

January 2006

12

January 5th

13

January 12th

14

January 19th

Warning /!\ UpstreamVersionFreeze

15

January 26th

February 2006

16

February 2nd

Warning /!\ Remaining upstream merges completed

17

February 9th

18

February 16th

19

February 23rd

Warning /!\ FeatureFreeze

March 2006

20

March 2nd

21

March 9th

22

March 16th

23

March 23rd

24

March 30th

April 2006

25

April 6th

Warning /!\ DocumentationStringFreeze

26

April 13th

Warning /!\ BetaFreeze

27

April 20th

Warning /!\ BetaRelease, Warning /!\ UserInterfaceFreeze

28

April 27th

Warning /!\ StringFreeze

May 2006

29

May 4th

30

May 11th

31

May 18th

Warning /!\ NonLanguagePackTranslationDeadline, Warning /!\ KernelFreeze

32

May 25th

Warning /!\ ReleaseCandidate, Warning /!\ LanguagePackTranslationDeadline

June 2006

33

June 1st

Warning /!\ FinalRelease

DapperReleaseSchedule (last edited 2008-08-06 16:28:30 by localhost)