Andrzej Bialecki wrote:
I usually follow these rules, which I propose to discuss/modify/accept:
* New features are first committed to trunk (or CVS HEAD). This way we
avoid losing new features somewhere on the branches, because as the time
goes it would be more and more difficult to forward-port them from past
branches to the trunk.
* If there are important features, which will benefit majority of users,
these are back-ported to release branches afterwards. I believe this is
the case with the ppt/xls plugins.
* other than that, the code in release branches is considered "stable",
i.e. no new features are introduced except for fixing some minor issues.
+1
Doug
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nutch-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-general
