This is my personal model for this stuff. YMMV
---- trunk -------+---- main development -----------
|
release branch branches/JCS_1_3
|
+ --- tag tags/JCS_1_3_RC1
|
+ --- tag tags/JCS_1_3_RC2
|
+ --- tag tags/JCS_1_3
|
+ --- tag tags/JCS_1_3_1
you release *from* a release branch *on* a release tag.
Best regards
Henning
On Wed, 2007-06-06 at 18:41 +0100, sebb wrote:
> On 06/06/07, Roland Weber <[EMAIL PROTECTED]> wrote:
> > Hi Thomas,
> >
> > >> If you changed the release files manually, you
> > >> should commit those changes to SVN and give Sebastian some time to
> > >> change his vote.
> > >
> > > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> > > SVN. This is at least what I understood the release-then-vote-policy
> > > means.
> >
> > The point of a SVN branch is to have an archived version of the
> > exact files that go into the release. If you have to change a
> > release after creating the branch, you should update the branch
> > and re-build the release from scratch. This is the best way to
> > make sure that releases can be reproduced.
>
> s/branch/tag/g surely?
>
> S///
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
|gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
