On Thursday October 19 2006 3:58 pm, Wendy Smoak wrote: > On 10/19/06, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > The problem is that this is not ALLOWED. The artifacts that were > > voted on MUST be the artifacts that are released. You cannot vote > > on one set of artifacts, then build a whole new set of artifacts for > > the release. > > In practice, this does actually happen. Jakarta Commons uses release > candidates, calls a vote, and then it's up to the release manager to > make the final changes (usually just the version number, maybe minor > editing of release notes,) and build/publish the final version.
Well, I was speaking based on experience in the incubator. The incubator rules/process pretty much mandates that if an issue pops up, we correct it, rebuild new artifacts, and re-vote on those specific artifacts. In anycase, the changes to the maven release plugins/processes definitely need to take the incubator process into account, especially since the only projects I'm involved in are incubator projects. ;-) -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
