-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Rob Church wrote:

...

tags/REL1_8_3/phase3/includes/DatabasePostgres.php
tags/REL1_9_2/phase3/includes/DatabasePostgres.php

WTF?

*No one* except the release manager is supposed to alter *tags*, ever. If code *has* to be backported, then it gets backported to a branch.

Have reverted them.

For reference, Subversion doesn't have "tags" in the sense that CVS does; to create an easily-referenced "tag" for a particular state of the code you clone a directory in the same was as you create a branch.

The good thing is this gives warm fuzzy feelings for being a clever implementation.

The bad thing is that the tagged version can still be changed, which makes things potentially a bit confusing. They need to be left intact so that we can continue to pull past revisions out of the repository for reference, reproduction of bugs, etc.

Apply fixes for release branches only in the *branch* directories, eg branches/REL1_8 and branches/REL1_9. New tag snapshots will be copied off of the branch directories at the next release.

- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)

Rob Church wrote: <snip>

*No one* except the release manager is supposed to alter *tags*, ever. If code *has* to be backported, then it gets backported to a branch.

I have added some documentation on mediawiki.org:

http://www.mediawiki.org/w/index.php?title=Subversion&diff=69044&old...

Go ahead and fix my English >)