2007/3/28, Andrzej Bialecki <[EMAIL PROTECTED]>:
Dennis Kubes wrote:
> Yes. This seems to have fixed the problem. All, do we want to create a
> JIRA and commit this for the 0.9 release?
It should definitely go into the release, and we need a patch for the
trunk/ .
+1
Actually, I'm somewhat surprised that we have tags/release-0.9 but we
don't yet have branches/branch-0.9 ...
IMO there's no need for a branch before a release.
I think I'm confused, or the release procedure is confused. My
understanding so far was that we first create a branch-0.9, we test the
build from that branch and if it passes all tests and the wait period is
over, then we copy it to tags/release-0.9 and proclaim a release - which
is really a read-only branch, i.e. we don't ever commit any patches to
it ... If that were the case, then we still wouldn't have the
release-0.9 tag, we could have applied the patch in branch-0.9, plus
possibly other patches, and then finally tag this tree as tags/release-0.9
.
IMO we should have had a 0.9-rc1 tag, apply patch to trunk, have 0.9-rc2 tag
and so on
until we are satisfied.
Then when we're actually satisfied create tag for 0.9 (copy from rc that got
promoted).
What is the benefit of using a branch before a release?
--
Sami Siren
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
