Hello, sounds good. one question is we have taged release-0.9, and this release has been there in some mirror sites of nutch, and people downloaded this version, so there would be two nutch-0.9 exist in the world, how could people differ between them.
Thanks David Chris Mattmann ： > Folks, > > Discussing this with Andrzej, and reading his email below, I tend to agree > more with this procedure below. I would like to call for a vote to change > the existing as-documented procedure (on the wiki) to branch first, do > testing in branch (apply patches where needed), and then when the branch > is blessed (e.g., 3 binding votes from committers in favor of it), tag it, > and make a release. Sound good? > > In terms of next steps with what we have now, that boils down to: > > 1. delete tags/release-0.9 > 2. apply patch to trunk > 3. create branches/branch-0.9 > 4. have dennis test again (large scale) > 5. if all goes well, finish release process > 6. tag tags/release-0.9 > > Thoughts? > > Thanks! > > Cheers, > Chris > > On 3/28/07 10:35 AM, "Andrzej Bialecki" <[EMAIL PROTECTED]> wrote: > > 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/ . > > > > Actually, I'm somewhat surprised that we have tags/release-0.9 but we > > don't yet have branches/branch-0.9 ... > > > > 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. > > > > As it is now we are in an awkward situation that we have to patch > > tags/release-0.9 .. > > > > One solution would be now to delete this tag, apply the patch to trunk, > > create branches/branch-0.9, and continue applying any other patches that > > may come up during this testing period - and when we are finally happy > > with the codebase then take a snapshot into tags/release-0.9, and keep > > it read-only. > > > > Another solution is to bend the rules and apply the patch to trunk/ and > > then merge from the trunk to tags/release-0.9 . > > > > What do you think? -- ------------------------------------------------------------------------- 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
