My +1
 > From: ol...@apache.org
> Date: Tue, 11 Sep 2012 10:30:27 +0200
> To: dev@mojo.codehaus.org
> Subject: Re: [mojo-dev] [VOTE] Release Cobertura Maven Plugin version 2.5.2
> 
> +1
> 
> 2012/9/10 Robert Scholte <rfscho...@codehaus.org>:
> > Hi,
> >
> > I'd like to release version 2.5.2 of the Cobertura Maven Plugin
> > This plugin provides the features of Cobertura within the Maven 2 & 3
> > environment.
> > The report generated by this plugin is the result of executing the Cobertura
> > tool against your compiled classes to help you determine how well the unit
> > testing efforts have been, and can then be used to identify which parts of
> > your Java program are lacking test coverage.
> >
> > We solved 3 issues:
> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11226&version=18781
> >
> > There are still a couple of issues left in JIRA:
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MCOBERTURA+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
> >
> > Staging Repositories:
> > General:  https://nexus.codehaus.org/content/groups/staging/
> > Exclusive:
> > https://nexus.codehaus.org/content/repositories/orgcodehausmojo-021/
> >
> > (Staging) Site:
> > http://mojo.codehaus.org/cobertura-maven-plugin/
> >
> > SCM Tag:
> > https://svn.codehaus.org/mojo/tags/cobertura-maven-plugin-2.5.2/
> >
> > Additional info:
> > This will be a bugfix release mainly due to to MCOBERTURA-151, a critical
> > issue which has already been solved a long time ago.
> > We've received several pings with requests for a new release.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > The vote is open for 72 hours and will succeed by lazy consensus.
> >
> >
> > Thanks,
> >
> > Robert
> 
> 
> 
> -- 
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
                                          

Reply via email to