On May 13, 2010, at 2:10 PM, Alan D. Cabrera wrote:
On May 13, 2010, at 1:15 PM, Kalle Korhonen wrote:
On Thu, May 13, 2010 at 1:01 PM, Alan D. Cabrera <l...@toolazydogs.com
> wrote:
Another quick comment. If you're using Nexus staging we don't
need to
increment 1.0.x. You can just drop the staging repository and
form a new,
fixed, one.
Well, that's a possibility in marginal cases depending on what went
wrong but the tag's created already at that point.
Good point. How about cutting a branch, say branches/1.0 and the
release manager, RM, has total control over it, i.e. nothing gets
added there w/out his explicit permission. The RM can cut a tag,
create a staging repo, then start a vote. If the vote fails he
deletes both the tag and staging repo. IIUC, deleting the tag is
kosher so long has it has not been blessed by the PMC by a release
vote. (Craig, do you concur?)
You can create as many 1.0.0 releases as you like, as long as the last
one is approved by the incubator PMC. A staging area directory is
typical. If the artifacts are bad for whatever reason you can delete
the tag, retag and respin until you get it approved. There is no
reason to bump the release number (e.g. 1.0.1, 1.0.2, etc.) due to a
failed artifact.
So I agree "what Alan said".
And a side comment. This has been a long incubation but I think you
folks have got it. Just turn the crank and get out of here. ;-)
Craig
Regards,
Alan
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
