Scott,
> The reason to keep branches to a min is that changes from one branch
to
> not
> affect another. So if we fix something in 0.8.3 branch, we also need
to
> fix
> all subsequent branches. Branches also require special changes to the
way
> we
> as developers work.
Sorry Scott, I am a little confused. Are we merging the changes in the
release branches back into the head? Using something like the syntax:
cvs update -j [main_trunk] -j [release_branch]
(stolen shamelessly from
http://www.netbeans.org/community/sources/branches.html)
In theory I think that it is a lot like generating patch files and just
applying it to the other branch. There is even a process identified on
the netbeans site (link above) that we might use as a template.
Clayton
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
