On 12/19/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
Figure we should get that going while we wrap up on 1.0.4 code, otherwise a 72 hour buffer (at the least). I'm not aware of any pending changes ATM, but if you have any, please go ahead. Some procedural bits, yell if incorrect: * I can't find the v1 tag (probably somewhere is Struts land, not sure) but the v2 tag will be at maven/tags
I suspect I forgot to tag it explicitly, but from "svn log" it looks like r430659 did the deed. * 'mvn deploy' master pom to staging repo (which should be the repo
of choice once the snapshot marker gets removed) and when vote passes do a *nix 'cp' on people of the 2/ directory and maven-metadata.* from the staging repo to the m2-ibiblio-repo. Wanted to confirm that the metadata copy, in particular, is OK.
For some reason I went through more work than this last time ... but I suspect it's because we had not formalized our staging process, and I was using my ~craigmcc directory. This sounds right (unless, as Wendy says, you want to live dangerously and try the repository updater :-). The updater should be our long term direction, unless/until the Maven release plugin does all the stuff we need for staging votes. -Rahul
A couple of notes on the master POM itself (as of r488876): * Is org.apache:apache:3 still the right parent for shale-parent? It should be unless they've published a new top level one. * I like the habit I've seen Rahul and others do in Commons, of adding <contributor> entries for those who have posted patches. A quick scan of our issues might be useful. Craig
