[haiku-development] Re: Wrapping up R1 alpha 2
- From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 19 Apr 2010 23:17:00 +0200
Hi Ingo,
On 19 April 2010 21:35, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 2010-04-18 at 12:32:36 [+0200], Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
>> > > * The release coordinator will monitor the ongoing trunk activity and
>> > > list
>> > > all change sets on a Wiki page. All release-relevant change sets will
>> > > need
>> > > to pass a review (by any other developer or by the release coordinator)
>> > > before being merged into the release branch. (**) The idea behind the
>> > > review process is to ensure a high quality of the changes that end up in
>> > > the release branch.
>> >
>> > I guess this does not differ from the previous workflow, but why not
>> > have devs put 'Alpha2' in their commit message. The manual work of
>> > maintaining a wiki page is replaced with the magic of a query.
>>
>> I'd like to have a table with a revision column and several manually
>> editable
>> columns (reviewer, comment, merged flag). If that can be done with a query,
>> then I'm all for it. I'd prefer an opt-out commit message tag ("-alpha2"),
>> so
>> forgetting it wouldn't do any harm.
>
> I've created [1] for tracking the trunk change sets and their review and
> merge status.
I'll try to whip up a script to see whether we can automate this. I
'll put it on my todo list for Wednesday.
Regards,
N>
Other related posts:
