+1
 
> From: ol...@apache.org
> Date: Sat, 21 May 2011 09:23:34 +0200
> To: dev@mojo.codehaus.org
> Subject: Re: [mojo-dev] [VOTE] Release cobertura-maven-plugin version 2.5.1
> 
> +1
> 
> 2011/5/20 Benson Margulies <bimargul...@gmail.com>:
> > Hi,
> >
> > I'd like to release version 2.5.1 of the cobertura-maven-plugin
> >
> > c-m-p is a maven plugin that executes the Cobertura code coverage tool.
> >
> >
> > We solved 3 issues, one of which was a regression in 2.5 release.
> >
> > ** Bug
> >    * [MCOBERTURA-132] - forkMode is ignored when generating cobertura
> > reports using Maven 3
> >    * [MCOBERTURA-145] - Regression: report will not be rendered on
> > invocation of mvn clean install site for a multi module project.
> >
> > ** Improvement
> >    * [MCOBERTURA-144] - The JIRA report should only list those issues
> > fixed in the current release
> >
> >
> > There are still plenty of issues left in JIRA (25), though many of
> > these are probably problems with cobertura itself that no active
> > developer on the plugin is prepared to diagnose.
> >
> > Staging Repositories:
> > General:  https://nexus.codehaus.org/content/groups/staging/
> > Exclusive: 
> > https://nexus.codehaus.org/content/repositories/orgcodehausmojo-031/
> >
> > (Staging) Site:
> > http://mojo.codehaus.org/cobertura-maven-plugin/
> >
> > SCM Tag:
> > https://svn.codehaus.org/mojo/tags/cobertura-maven-plugin-2.5.1/
> >
> >
> >  [ ] +1
> >  [ ] +0
> >  [ ] -1
> >
> > The vote is open for 72 hours and will succeed by lazy consensus.
> >
> >
> >
> > Yr Obedient Servant,
> >
> > bimargulies
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >    http://xircles.codehaus.org/manage_email
> >
> >
> >
> 
> 
> 
> -- 
> Olivier Lamy
> http://twitter.com/olamy | http://www.linkedin.com/in/olamy
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
> http://xircles.codehaus.org/manage_email
> 
> 
                                          

Reply via email to