Jérôme Charron wrote:
Thanks Michael for this status about these plugins.
Since the best way to widely test and improve these plugins is to widely
using them,
I thing it's time to commit them.
If there is no objections in the next days, I will commit them next week.
However, my first idea was to commit these patches in the trunk in order to
avoid introducing
some new bugs in the future 0.7.1 release. Committers (especially Piotr, our
release expert) and developpers, what do you think about this point? (trunk
for 0.8, or 0.7 branch for 0.7.1)
+1 on committing to the trunk. -0.5 to committing to Release-0.7 :-) See
below.
We have to work out a consistent policy on release engineering model,
and a policy on committing new functionality, with regard to the releases.
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.
This is an important distinction, because users will expect the
Release-* branches to work properly at all times - i.e. at any given
moment they should be able to get the code, recompile it and it should
work properly - of course, within the functional limits of the given
release. This is not the case with the trunk/ or HEAD, where active
development occurs, and where occasional breakage may happen and may
last even for longer time, and this is acceptable there.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
-------------------------------------------------------
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
