Am 03.05.2015 um 10:42 schrieb Benedikt Ritter:
Nope, that's not how Apache works (at least in my opinion :-) ). I've
planned to push a release but then good caught up with other stuff.
Here is the list of things that should be resolved for 1.3 [1]. If
people jump in and help by providing patches (or PR via github [2]).
This will speed up the process of pushing out a new release. Now that
groovy is part of the Apache family, I would love to see this kind of
inter-project collaboration happen.
br,
Benedikt
[1]
https://issues.apache.org/jira/browse/CLI-179?jql=project%20%3D%20CLI%20AND%20fixVersion%20%3D%201.3%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
[2] https://github.com/apache/commons-cli
Hi Benedikt,
thanks for the information. :)
For course I hope that somebody steps up and helps closing these issues.
From a short glance at the issues I'm not convinced that they are
really blocking a release.
The last release of commons cli was on 2009-03-19 and there are already
a lot of bugs fixed and features added:
https://issues.apache.org/jira/browse/CLI-193?jql=project%20%3D%20CLI%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.3%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
People have been waiting for a release for a very long time now. So I
would suggest postponing the issues to 1.4 and going ahead with the
release of 1.3. :) (Of course that's not for me to decide.)
- Pascal
