Not sure I agree wrt the jira project. It clearly states in the performing a release guideline to create the jira project when preparing for the production release. If you're intending to do a production release, I see no problem creating the jira project before the vote. If the vote is turned down, you'll get feedback on what to fix. Eventually it will be released so why not fixing everything that can be fixed in advanced?
/Anders On Mon, Oct 31, 2011 at 20:42, Robert Scholte <[email protected]> wrote: > Here we're having the same problem as graduations from the sandbox: Some > parts of the pom can only be made final once the vote has passed. > It's kind of sad if we need 2 rounds of votes for these promotions. > AFAIK there's no description about this in detail. > > My suggestion is: > release the plugin with the suggested version, but keep the scm/jira as it > is. > If the vote passes, drop the release, make the required modifications, > re-release and publish it. > During the vote NO modifications are allowed. > > this way we can keep it to a single vote without any damage if the vote > won't pass. > > WDYT? > > -Robert >> Date: Mon, 31 Oct 2011 12:27:18 +0100 >> From: [email protected] >> To: [email protected] >> Subject: Re: [mojo-dev] [VOTE] First production release of >> sonar-maven-plugin >> >> IMO it's a blocker. Everything should be fixed in the staged release. >> >> /Anders >> >> On Mon, Oct 31, 2011 at 11:37, Simon Brandhof <[email protected]> >> wrote: >> > Hi there, >> > >> > The sonar mojo is still a beta version but it's used in production for a >> > long time (a few years). For this reason I think it deserves to upgrade >> > to >> > versions 1.0 (for maven 2) and 2.0 (for maven 3). >> > A few issues have been resolved since last release, particularly the >> > possible conflict of commons-lang with some sonar plugins (see >> > MOJO-1763). >> > >> > Release 2.0 for maven 3 : >> > >> > Release notes : >> > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=18040 >> > Staging repository : >> > https://nexus.codehaus.org/content/repositories/orgcodehausmojo-023/ >> > >> > Release 1.0 for maven 2 : >> > >> > Release notes : >> > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=18041 >> > Staging repository : >> > https://nexus.codehaus.org/content/repositories/orgcodehausmojo-024/ >> > >> > About the release process, docck:check is ok but I didn't create the >> > dedicated JIRA project. It still uses the component "sonar" in the Mojo >> > project. Is it blocker ? If yes, can an administrator create it please ? >> > >> > The vote is open. >> > >> > Thanks >> > >> > Simon Brandhof >> > www.sonarsource.com >> > twitter.com/SimonBrandhof >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
