postfixadmin-devel

Re: [Postfixadmin-devel] SF.net SVN: postfixadmin:[414] branches

[Christian B. <pos...@cb...>]

Hello,

Am Mittwoch, 23. Juli 2008 schrieb Gin...@us...:
> Revision: 414

> yeah, clearly I should have created the branch before merging stuff
> into 2.2.1...
>
> Added Paths:
> -----------
>     branches/postfixadmin-2.2.1.1/

What about using another scheme for branch names and version tagging?

Proposal:
    branches/postfixadmin-2.2 (a branch for all 2.2.* code)
and
    tags/postfixadmin-2.2.1.1 (a tag for each release, code in read-only 
    mode - no commits in tags/*)

This avoids the need to rename the branch after every minor release.
It would also bring some benefit for our users - we could just tell them 
to use branches/postfixadmin-2.2 and run svn up from time to time 
without the risk to break something.


Regards,

Christian Boltz
-- 
Error: File not found -- search behind couch? (Y/N)

Re: [Postfixadmin-devel] SF.net SVN: postfixadmin:[414] branches

[David G. <da...@co...>]

Christian Boltz wrote :
> Hello,
> 
> Am Mittwoch, 23. Juli 2008 schrieb Gin...@us...:
> > Revision: 414
> 
> > yeah, clearly I should have created the branch before merging stuff
> > into 2.2.1...
> >
> > Added Paths:
> > -----------
> >     branches/postfixadmin-2.2.1.1/
> 
> What about using another scheme for branch names and version tagging?
> 
> Proposal:
>     branches/postfixadmin-2.2 (a branch for all 2.2.* code)
> and
>     tags/postfixadmin-2.2.1.1 (a tag for each release, code in read-only 
>     mode - no commits in tags/*)
> 
> This avoids the need to rename the branch after every minor release.
> It would also bring some benefit for our users - we could just tell them 
> to use branches/postfixadmin-2.2 and run svn up from time to time 
> without the risk to break something.
> 
> 

sounds good to me.

David


-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]