forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: Release Process...
Date Tue, 09 Sep 2003 08:36:32 GMT
Andre Anneck wrote:

> Hi dev-team,
> 
> in order to circumvent such conflicts I recommend using CVS branches (early branching):
> 1. Announce Code-Freeze
> 2. Open branch RC_0-5
> => Now people can continue work on MAIN, without interference of the release branch
> 3. Start tagging inside the branch to test release candidates (Maybe Tag-Names == Jira
Release-Names)
> => Bugs fixed in release branch need merge into MAIN branch, ok thats the overhead
work you have using this approach
> 4. Once satisfied with stability of RC_05, do the final TAG and produce the release artifacts.

+1

For now we can simply revert the last changes and release from that, but 
next time I propose we follow this process.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------



Mime
View raw message