Hi Niels, Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote: > I took some time to build a list of tasks that we need to release > alpha 1. See the wiki for the complete list of tasks, with their > respective task owners. Nice one! > d) Set up a test framework (what tests need to be passed in order to > qualify a build as 'good'?) Whatever you plan here, it sounds like it cannot be automated in time : -) So this would probably boil down to a tester that does the final acceptance test. > 2. RELEASE PREP > a) find mirrors What I miss here is: who will distribute the final images to the mirrors? Also, due to the first boot work (like MIME type setting), we thought about starting the image once before distributing it. However, I'm not sure this is a good idea, and it also doesn't solve the issue for CDs where it would be the most interesting. In any case, care must be taken that the SSH keys are still generated on the next boot, and are not included in the image. > b) Write release notes (all known issues) > c) Write press release > d) Determine press plan (in other words, do we go big on this one or > will we keep it small) While it's a big one for us, it's only an alpha release, so I would prefer to keep it smaller rather than bigger. That doesn't mean it shouldn't get spread wide, just with small rather than big words :-) BTW we still have some Be headers left that need to be replaced, and I'm not sure we can really distribute them as is. > 4. RELEASE > a) branch the source tree (Axel) Accepted, though it will be in the evening or early morning, whatever is preferred (as I'm not available in between). Bye, Axel.