Re: [Babeldoc-devel] 1.2 Maintenance branch

[Michael A. <mic...@ze...>]

Hi,

That's exactly what I've done: create a branch tag for 1.2 maintenance,
and left 1.3 development on the head.  I noticed that there is a 1.3
revision tag, but I think it's spurious.  I think we can probably get
rid of it.  Anybody using it?

Anyway, branching the maintenance and leaving development on the HEAD
seems to be standard practice.  CVS does require you to create a
revision tag at the base of a branch, so that the branch can be merged
with other branches, which I've done (it's the V1-2_Root revision tag).

So, I think we're all set for 1.3, although we can rename the tags if
necessary later.

Hope the conference is going well.  I haven't been to Belgium yet; guess
I should find a conference there sometime and get myself over ;-)

Cheers...


MikeA



On Wed, 2003-12-03 at 13:06, Bruce McDonald wrote:
> I think that we should stick with this convention - it makes sense.
> 
> On Wednesday 03 December 2003 05:51 am, Dejan Krsmanovic wrote:
> > Great Mike!
> > We had established some naming convention for braches
> > and tags but I cannot remember now (I am in Belgium
> > right now on Java Polis conference!). We can rename it
> > later.
> > When we had released 1.0, we created maintanance
> > branch for 1.0 and development was on HEAD. I am not
> > sure if we should perform the same rules now. What do
> > you (and others) think?
> >
> > Dejan
> >
> > --- Michael Ansley <mic...@ze...> wrote:
> > > All,
> > >
> > > I've created a branch for maintenance of 1.2.  The
> > > branch tag is V1-2,
> > > the branch root tag is V1-2_Root.
> > >
> > > Please make sure that if you fix and commit
> > > something in the 1.2 branch
> > > that somebody merges the changes to the HEAD.
> > > Otherwise we'll get
> > > regression problems.  If you're not sure, let me
> > > know.
> > >
> > > Any other issues, please let me know.
> > >
> > > Cheers...
> > >
> > >
> > > MikeA
> >
> > -------------------------------------------------------
> >
> > > This SF.net email is sponsored by: SF.net Giveback
> > > Program.
> > > Does SourceForge.net help you be more productive?
> > > Does it
> > > help you create better code?  SHARE THE LOVE, and
> > > help us help
> > > YOU!  Click Here: http://sourceforge.net/donate/
> > > _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> >
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Free Pop-Up Blocker - Get it now
> > http://companion.yahoo.com/
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?  SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel