- From: Linss, Peter <peter.linss@hp.com>
- Date: Tue, 15 May 2012 19:38:56 +0100
- To: Public CSS test suite mailing list <public-css-testsuite@w3.org>
I'm going to be landing a bunch of changes to the way Shepherd handles Mercurial revision data, namely better handling of cross-asset renames and merge changesets. To go with these changes, I'm going to rebuild the entire repository history database. I expect this process to take anywhere from 30-60 minutes. To minimize impact, I'm going to do the rebuild this evening around 7pm PDT. Shepherd will be unavailable during the maintenance, but pushes to the test repository are fine (Shepherd will pick up the changes after the rebuild). I'll send out another email when I actually start, and another when it's back online with more details about the changes. Note that asset history fragment IDs will be changing as part of the update, so if you have bookmarks to a specific revision or comment, such as: http://test.csswg.org/shepherd/testcase/absolute-non-replaced-height-001/#event-8 you will need to update the fragment ID afterwards. It will be something like: http://test.csswg.org/shepherd/testcase/absolute-non-replaced-height-001/#revision-2197-daadee1cbb60 The new fragment IDs should be stable (they are based on a hash of the revision or comment). This allows the addition of older revisions (as happens with branch merges) without changing event IDs. Peter
Received on Tuesday, 15 May 2012 18:40:39 UTC