> -----Original Message----- > From: Lukas Theussl [mailto:ltheu...@gmail.com] On Behalf Of Lukas Theussl > Sent: Monday, 20 June 2011 7:25 PM > To: Maven Developers List > Subject: Re: [VOTE]: release maven-changes-plugin 2.6 > > > > Gavin McDonald wrote: > > > > > >> -----Original Message----- > >> From: Benson Margulies [mailto:bimargul...@gmail.com] > >> Sent: Sunday, 19 June 2011 6:08 AM > >> To: Maven Developers List; Maven Project Management Committee List > >> Subject: [VOTE]: release maven-changes-plugin 2.6 > >> > >> Hi, > >> > >> We solved 3 issues: > > > > Really? You'd release a product after solving 3 issues? > > > > Having looked at those 3 issues I believe it can wait for more. > > Really? And what in your opinion would be the threshold for a release? 5 > issues? 16? And if there are no open issues left, do we have to wait for > people to find 8 more before we can release it?
Depends on the quality and quantity, whether it fixes a security issue, introduces a new must have feature, etc. I would happily vote +1 for a one line security fix. Context is everything. > > Seriously, I think this posting will easily make it on our list of 10 most > pointless > contributions of the year. Do not criticise me for making a vote statement. It was not a contribution, it was a statement regarding the vote, which anyone is entitled to do. > When to call a vote for a release is solely the > decision of the release manager, and the number of issues is simply > irrelevant. Of course, but am I not entitled to express my vote and supporting statement, or are all votes expected to be +1 with no comments. What do you base your vote on exactly? Rolling a new release for a few lines of code that fixes a couple of bugs and does not introduce any new functionality is overkill IMHO. But I will stay out of such votes/threads/opinions in the future , do what I joined this list for, then leave when I'm done. Gav... > > -Lukas > > > > > > Don’t release for the sake of releasing. > > > > Gav... > > > > +-0 non-binding > > > > > >> > >> http://jira.codehaus.org/browse/MCHANGES/fixforversion/17375 > >> > >> > >> There are plenty of issues left in JIRA: > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQue > >> ry= > >> > project+%3D+MCHANGES+AND+status+%3D+Open+ORDER+BY+priority+DE > >> SC&mode=hide > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-024/ > >> > >> Staging site: > >> http://maven.apache.org/plugins/maven-changes-plugin-2.6/ > >> > >> Guide to testing staged releases: > >> http://maven.apache.org/guides/development/guide-testing- > releases.htm > >> l > >> > >> Vote open for 72 hours. > >> > >> [ ] +1 > >> [ ] +0 > >> [ ] -1 > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > >> additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > > additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional > commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
