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

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Fri, 23 Apr 2010 01:33:10 +0200


On 22 April 2010 17:25, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 2010-04-22 at 15:48:07 [+0200], Niels Reedijk <niels.reedijk@xxxxxxxxx>
> wrote:
>> 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:
>> http://dev.haiku-os.org/wiki/R1/Alpha2/MergeTrackingTest
>> 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?
> Sounds good, thanks!

I have added yet another iteration of the script. Please see the page
for details on what it does. Basically: it does automatic markup, it
distinguishes between change sets that need to be reviewed, that need
to be merged, that are merged and those that should not merge. No more
manual layouting is needed.

Note that the actual update of the mark up depends on when a new
change set is added to the list, only then the script will reformat.

Other related posts: