I was initially confused by this, but now that I understand its a full Maven release, I'm +1. I agree with 2.0.2. Note that the branch needs to have its versions converted - it was copied directly from the previous tag so the versions are not snapshots. Perhaps the part of the release plugin that does that could be factored into something exposed by another mojo? release:changeVersion, for example.
We need to fix the reporting API as well. I'm working on it. I'd like to suggest we take a little more time to test the solutions in place for these issues so that the release can stand up for the next month or so before the next scheduled release. - Brett John Casey wrote: > Hi all, > > If you've been watching this list, the users list, or JIRA, I'm sure > you've noticed that we managed to introduce some new bugs in 2.0.1. > Some of these are critical, and will block the use of this version. > > What I'd like to do is release a bugfix version, 2.0.1-1, to address > these critical issues. I've opened a new version on the Maven roadmap > in JIRA (http://jira.codehaus.org/browse/MNG) to track these. > Currently there are two, and I don't expect that number to climb much > more. > > Please note, this release is only for critical bugs. We're not going > to be fixing anything that we can limp along without for a bit longer. > > Because of the hurried nature of this vote, this email thread will > undoubtedly serve as a mechanism for determining which issues are > critical to release here; I will make sure JIRA reflects this discussion. > > Here is my +1. > > Sincerely, > > John > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
