[haiku-development] Re: Task list for alpha 1
- From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 22 Aug 2009 21:50:38 +0200
Hi!
2009/8/21 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
>> 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.
Well, or rather define it like x number of machines it should run on.
Or that everyone that tested one of the pre-alpha images should report
success on the final alpha image.
>> 2. RELEASE PREP
>> a) find mirrors
>
> What I miss here is: who will distribute the final images to the
> mirrors?
I would say that Matt (the buildmeister) will also seed the final
images to their destinations. He can work with Urias in getting them
where they should be.
> 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.
Ok. Is this a task big enough that it needs its own ticket or its own
entry in the todo list?
>> 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 :-)
Yes. I have offered to work on the draft press release. I will spread
this internally to discuss and improve on it. I'd rather not put this
on a mailing list because of the possible misunderstandings from
outside.
> 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.
Ok. This should probably be a new ticket so we can track it.
>> 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).
Well, let's put it in the evening then. What should be the name?
I would suggest /haiku/branches/haiku/R1.0-alpha1 (because there might
be an R1.5-alpha branch series in the future).
N.
Other related posts:
