Hello, This is my take on the alpha 1 release window. Points of attention: * Even though this is an alpha release, it is also our very first release and as such require a certain amount of polish. I agree with the sentiment that it should not be a big deal for an alpha, but we have been building a lot of anthicipation over the past few years, as such I built in a (small) bug fix cycle in. * The website team needs time to prepare for the release, either with the new website theme (drupal 6) and/or with adaptations of the structure of the website * The marketing department needs to get started. * Since it is now summer holidays (in many many places) I think a start date of August 15th is to shorthand. I propose we give people a bit more time to finish their projects. I propose the following: ### Tuesday September 1st 12:00 GMT: - Feature freeze. Only bug-fixes are allowed. The exact definition for a bug fix might be difficult, but we can rely on the self-regulation of the developer group to make sure nothing creeps through During this phase we can start the first test-builds with a selected group of individuals who will make the final builds. These builds will be internally tested. Also, during this one week I hope we can get all developers to close at least one or two bugs as a bit of polish for the release. ### Wednesday September 9th 12:00 GMT: Tag made in Subversion. I propose not yet opening the repository just yet, as I hope that all developers will test the final image one last time. ### Saturday September 12th, 12:00 GMT: If no big issues were found during testing, the images will be distributed to all the mirrors. As soon as that process is done, the websites are updated and press releases will be distributed. The repository will be reopened. That's about my plan. Ideas? Opinions? Next I'll dig up some of my (preliminary) notes on what needs to be done before we get the release out. Kind regards, Niels