- From: Linss, Peter <peter.linss@hp.com>
- Date: Wed, 16 May 2012 05:38:03 +0100
- To: Public CSS test suite mailing list <public-css-testsuite@w3.org>
Sorry it took a little longer than expected, best laid plans and all that… As always, if you notice any issues or missing/corrupted data, please notify me immediately. I have backups... The major change to the system is the way it handles merge changesets. Shepherd now fully deals with branches and merges and tracks each file's history independently on each branch that it exists in. When merges are landed now, Shepherd should "do the right thing" (it actually handles merges better than Mercurial's own web UI does). I'm still looking for a good way to visualize the branches in the asset history, if you have any ideas, let me know... Along the way I also added code to handle when files are renamed or moved in such a way that they are bound to different assets as a result. When this happens now, the revision log in Shepherd contains links bi-directionally between the involved assets. It also copies the past history of the file to the new asset, as if it was associated to the new asset all along. As a result of these changes, asset's statuses and comments are now more closely bound to the revision in which the status changed or the comment was entered. For the most part, you won't notice, but if you enter a comment on (or change the status of) a past revision of a file, you might see the difference. This was done to allow sane processing when branches are merged and contain revisions older than the current state of the asset. Shepherd also got a new 'maintenance mode', which you will have seen if you tried to use it in the past two hours, and the ability to rebuild the entire history database without losing user entered data. A few bug fixes and minor features happened along the way as well. Peter
Received on Wednesday, 16 May 2012 04:41:49 UTC