SteveKing wrote:
> Hi,
>
> I'd like to propose a release procedure for TSVN which might actually
> work. The one we tried first simply can't work reliably because there
> are too few TSVN devs around to get votes for revisions to be
> backported to the release branch (right now, only Simon and I can
^^^^^
I think you mean Will. I have some familiarity with TBlame and SubWCRev
but am out of my depth with the shell extension.
> really vote on code changes, and if we require two votes for a
> backport, that would mean a 100% agreement).
>
> So here's my draft for a release procedure:
>
> - about a week before a new release, which can be initiated by any
> dev, we create a branch from /trunk for that release
> - the nightly builds switch from /trunk to that branch so that from
> this time on users can test the release candidate
> - bugs found and fixed during that time are fixed on /trunk, and
> mentioned in a Backport.txt file on the branch
> - the dev who fixed that bug decides himself if it should be
> backportet or not, and if yes merges it to the release branch right
> away - if another dev then objects to that merge (of course always
> with an explanation why) that fix get's undone on the branch. I don't
> think that will happen very often though.
> - after about a week, the release branch get's tagged and released.
>
> Comments?
+1. That seems exactly the right level needed for TSVN releases. Can you
put that procedure in a text file on trunk?
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Jan 16 19:00:00 2005