Am 2017-01-25 um 22:08 schrieb Christian Schulte:
Am 01/25/17 um 20:53 schrieb Michael Osipov:
Am 2017-01-22 um 13:58 schrieb Michael Osipov:
Am 2017-01-22 um 11:22 schrieb Stephen Connolly:
I'm currently waiting on Hervé to start the 1.0.3 release of resolver.
Once we get that I'm going to start cutting RCs (I plan 2 a week apart)
Once we have a stable RC I will cut the release, and start a clock
towards
3.5.1 (6 weeks approx)
If you miss the boat, you can catch the next one, but we need to get this
project into a rhythm.
I started already working on the blessed issues. Do I need someone's
else consent to merge my issue branch into master assuming that it
passes the build in Jenkins?
I still have an unagreed list of issues for FIX-3.5.0:
MNG-5538 mvn start script causes cygwin warning
^
FIX-3.5.0
MNG-5567 Zip files are not included in classpaths at all
^
FIX-3.5.1 as 3.5.0 no longer would be a drop in replacement.
MNG-5579 Unify error output/check logic from shell and batch scripts
^
FIX-3.5.0
MNG-5823 mvnDebug doesn't work with M2_HOME with spaces - missing quotes
^
FIX-3.5.0
MNG-6144 DefaultWagonManagerTest#testGetMissingJarForced() passed
incorrect value
MNG-6145 Remove non-existent m2 include in component.xml
MNG-6146 Several small stylistic improvements to code and documentation
Haven't looked at those. If they stop making 3.5.0 a drop in replacement
for 3.3.9, I'd say FIX-3.5.1.
The first fixes only a test, no main code change. The second removes a
non-existent ref, no-op. The last one is either docs or formatting
improvement.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org