Hello,
I think a lot of people will wait before moving to mapreduce
implementation for some time so we will have a 0.7 version to support.
I was a heavy CVS branch user in my previous job taking care about
common library so I fully agree that such branch would be needed for bug
fixing. I would go (as Doug suggested) for "lazy creation" mode of this
branch - should be created on first need to commit to it.
I also tracked down version numbers in nutch source code:
1) CHANGES.txt - that was easy all releases are listed here
2) default.properties
version=0.7-dev
3) nutch-default.xml
<property>
<name>http.agent.version</name>
<value>0.07</value>
<description>A version string to advertise in the User-Agent
header.</description>
</property>
So we have a small inconsistency in naming versions (I have commited
0.07 in nutch-default.xml yesterday but it used to be 0.06 so I have not
changed the format) - I will fix soon.
I think we all refer to 0.7 as next number (and 0.6 as current) so
nutch-default.xml contains wrong format. In fact it should still contain
-dev suffix.
To make undocumented comvention documented I would also like to suggest
naming releases with X.Y format and naming code developed to make a
(release X.Y) X.Y-dev.
I will try to put a draft of doc on Release HOWTO on Wiki tommorow.
Regards,
Piotr
Andrzej Bialecki wrote:
Doug Cutting wrote:
We may want to start a branch for the release too, as described at:
http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-ch-4-sect-4.4.1
If we think we may someday want need 0.7.1 release, then we will need
a 0.7 branch to make this from. We can start this branch later by
basing it on the 0.7 tag. But we should never alter the 0.7 tagged
code once it is created.
Thoughts?
I agree. I have a similar experience from another OSS project (FreeBSD),
where this schema is being used extensively. This allows to provide some
limited maintenance for past releases. Considering that this is the last
release before merging the map-reduce, doing a branch seems very
appropriate.
-------------------------------------------------------
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-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
