[haiku-development] Re: Wrapping up R1 alpha 2

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Thu, 22 Apr 2010 15:48:07 +0200


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 have written a script that takes new changesets, checks if they are
in 'haiku/trunk' and if so, add them to the top of the wiki page. See
the test page at:


Everything can be safely edited, except:
 * The header. The offset of the table is hardcoded in the script, as
well as the header itself.
 * The topmost revision number and position in the table. The rest can
be edited and resorted at will (though this has no use). The topmost
revision is used to determine where to start looking for changesets.

The script adds new commits, adds their authors and guesses their
component by taking a random file change in that commit and taking the
name of the last directory in the path. On the test page this works
well for all commits except pulkomandy's.

The script runs every 15 minutes on a test version of the merge page.
If it works the next hours I will apply it to the real page. Screwups
can be reasonably easy corrected as the history feature of Trac keeps
us happy.

Any opinions?


Other related posts: