Re: [Babeldoc-devel] 1.2 Maintenance branch

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

Yes, you're right, it does need to be done on a periodic basis, so that
we have controlled tag points for each merge.

Bruce, this needs to be taken into account at each release point.  I
think that the policy should be that each point release of 1.2 must be
merged, and any outstanding issues in the maintenance branch should be
merged at the 1.3 milestone releases.  Is this feasible?

Cheers...


MikeA


On Wed, 2003-12-10 at 09:57, Hans Benedict wrote:
> On 2 Dec 2003, Michael Ansley wrote:
> 
> > 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.
> 
> Do we have a policy about who is when performing these merges? Propably it
> is a good idea to do this just before the next release in the HEAD branch?
> 
> Regards,
> Hans
> 
> 
> 
> -------------------------------------------------------
> 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