Folks, A couple of thoughts in response to Stephen:
The convention seems pretty clear to send a 'yoo-hoo' before starting a release in case anyone is dying to add something. Since I had to do that anyway, I thought I might as well solicit input on the version number. I did get poked once about the sensibility of releasing on a short list, albeit from a visitor, but he is a very distinguished visitor, so that left me cautious. Off I go. In fact I need to run a component release first. --benson On Tue, Nov 29, 2011 at 3:44 AM, Olivier Lamy <ol...@apache.org> wrote: > +1 > > 2011/11/29 Stephane Nicoll <stephane.nic...@gmail.com>: >> +1 >> >> On Tue, Nov 29, 2011 at 9:32 AM, Kristian Rosenvold < >> kristian.rosenv...@zenior.no> wrote: >> >>> Judging by the current set of changes, I'd go for 2.2.2 >>> >>> Kristian >>> >>> Den 29.11.2011 09:27, skrev Stephen Connolly: >>> >>> if you are stepping up to make the release, you decide the version number, >>>> and you decide if there is enough of a change to merrit your effort. >>>> >>>> sounds like you feel it is worth your time and you are adding a feature, >>>> so >>>> it is not a bug fix => 2.3 or 3.0 depending obey how big that feature >>>> feels >>>> to you >>>> >>>> - Stephen >>>> >>>> --- >>>> Sent from my Android phone, so random spelling mistakes, random nonsense >>>> words and other nonsense are a direct result of using swype to type on the >>>> screen >>>> On 29 Nov 2011 01:18, "Benson >>>> Margulies"<bimargulies@gmail.**com<bimargul...@gmail.com>> >>>> wrote: >>>> >>>> I just added a feature I care about, and there's a short list of others >>>>> pending. >>>>> >>>>> By the way, I had to go clear the fix versions from a slew of open >>>>> JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, >>>>> JIRA will include open jiras in the release notes if they have the >>>>> appropriate fix version. >>>>> >>>>> Please advise as to the next version #: 2.2.2 or 2.3? >>>>> >>>>> To save you the trouble of checking JIRA, here's what would ship as a >>>>> release today. I think that 570 implies that some others complaining >>>>> of related items are also fixed. >>>>> >>>>> >>>>> Release Notes - Maven 2.x Assembly Plugin - Version 2.3 >>>>> >>>>> >>>>> >>>>> ** Bug >>>>> * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby >>>>> * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 >>>>> * [MASSEMBLY-561] - Encoding is broken when filtering is enabled >>>>> * [MASSEMBLY-570] - dependency includes filters don't match >>>>> wildcard (*) in middle of coordinate segment >>>>> * [MASSEMBLY-581] - Allow formats in configuration to override >>>>> descriptor >>>>> >>>>> >>>>> ** Improvement >>>>> * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin >>>>> >>>>> >>>>> >>>>> ** Task >>>>> * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an >>>>> Apache license >>>>> >>>>> ------------------------------**------------------------------** >>>>> --------- >>>>> To unsubscribe, e-mail: >>>>> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> >>>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>>> >>>>> >>>>> >>> >>> ------------------------------**------------------------------**--------- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > 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
