db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Dudziak <to...@first.gmd.de>
Subject RE: [CVS] how to merge fixes between main trunk and rc5 branch?
Date Thu, 18 Dec 2003 15:16:08 GMT
On Thu, 18 Dec 2003 oliver.matz@ppi.de wrote:

> Hello,
> > -----Original Message-----
> > 
> > I guess before a final 1.0 relese all changes, fixes for 1.0 and new 
> > features should be checked into the main HEAD trunk.
> I disagree.  Fixes should be done in the oldest supported
> version and than merged into the newer ones.
> Otherwise you might unintentionally merge new source code
> in the maintenance branch.
> I our case that means: if there is a bug in 1.0.x and 
> in the trunc, decide whether a fix in the 1.0.x branch 
> is desired.  If so, fix it in that branch and than merge 
> it into the trunc.  Otherwise, document it in the 1.0.x 
> branch as "won't fix" and fix it in the trunc.

>From what I understand, does that mean that:

* Until 1.0 final is released

    - Any bugs/new features are maintained in HEAD and the branch

* After 1.0 final is released

    - New features and fixes for HEAD bugs are integrated into HEAD
      and - if bugs and pertaining to 1.0 too - backported to the branch
    - Bug fixes for 1.0 are integrated into the branch and - if still
      applicable - into HEAD

If so, then I don't quite see a reason why the maintenance branch is
created before the 1.0 release ? In all other respects this would be
similar to the Linux kernel model afaik.


To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message