Le 12/09/2012 14:04, Gilles Sadowski a écrit : > Hello. > > This thread was left alone for some time, although the main issue was not > settled: I requested the release of a new version of CM. > > I quote my remarks from an earlier message in this thread: > >> [...] issues resulted in some work being done, [...] >> My opinion is that releases must reflect that fact. Or, conversely, only >> "nothing new happened" is a reason for not providing a new release. >> >> Of course, there should be a balance between the work imposed by preparing a >> release, and the updated contents to be released. I think that the trade-off >> is already largely positive. > > and > >>>> "Wish" or "improvement" issues that miss a patch should not be blocking the >>>> 3.1 release. > > and > >> Of course, I'd be all for setting a date for release 3.2 too! > > Context: > I have to abide by the requirement to use an _official_ release of CM and my > code relies on bug fixes present in the development version. > > Are there any technical reasons to object to the starting of the release > process?
I would also be glad to see 3.1 out. As far as I am concerned, the work on differentiation is almost ready. If we can solve the silly problem I mentioned in another message a few minutes ago, I would be happy to finish that and release 3.1. Luc > > > Thanks for your attention, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
