> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mercredi 13 octobre 2004 01:37 > To: Maven Developers List > Subject: RE: Release of Checkstyle plugin v2.5 > > > I have pondered this. In the end, I didn't see any reason not to release > as: > > > > 1/ It had an important new feature (the support for checkstyle > suppressions > > filter) > > 2/ I think it's better to release than not to release in general (the > last > > release was 5 months old which is a long time) > > 3/ The code was tested, including the suppressions filter which I use > (as > > you have rightly found out on Cargo) > > While I agree with this, I think the release point is a bit arbitrary. I'd > prefer bug reports to be addressed before release - it seems wrong to me > to > release something with known issues, unless there is a specific problem > with > fixing some of them.
Actually there is... time (lack of) :-) > > > 4/ Nobody has shouted when I sent the email mentioned I was about to > release > > it. You sent a -0 which I interpreted as "I won't help and I'd rather > you > > perform a snapshot but I won't prevent you from releasing a version". > > That's what I meant - I was just looking for a reason that the release was > needed. > > > Now let me ask you a question: is there any issue in releasing quickly > > plugins provided they have been tested? > > I think there should be a reasonable expectation from the users that a > point > release has most if not all known issues resolved, as I've said above. Ideally yes, I agree with you. But if we do in our current state (i.e. committers involved, etc), it'll never happen. Or it will but only once a year. I think it's better to have frequent releases with no everything fixed rather than a single release every year with everything fixed. What I do find extremely important is to make it clear what is in the release. And this we're doing nicely with both the changes report and the announcement plugin. It's not like we're telling users we've fixed everything and they find it's not true. > > In the case of checkstyle where it has been 5 months, you're right - its > reasonable to release with 1 new feature because there are unlikely to be > any > new ones coming up. But bugfixes are important. > > > The only problem I can see is doing what Maven has done: i.e. almost > never > > releasing anything and thus building the expectations from the user that > the > > next release is going to be a big thing. > > I don't think this is exactly true. There have been a number of small > releases > of plugins that people have been looking after for the past few months. I was only talking about Maven core, sorry. > > Now I may be completely wrong and missing something important. In that > case, > > please accept my apologies. > > I don't think there's any problem - so I apologise if I came across too > strongly. In essence I would have liked to see done differently: > - reasoning given for the release after my initial questioning > - all known issues resolved or deliberately deferred before a point > release. > > Anyone else have thoughts on this? Ok, I'll explain it better next time. Maybe the fact that the release was fixing an important limitation with checkstyle suppressions filter was not made visible (I have remarked to myself - after the release - that the changes.xml description for this feature is not very explicit...). Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
