I'll start preparing a release soon. The current state is good enough
for a release, the remaining issues can be postponed to CLI 1.3.
I'd like to release a "long lived" release candidate (at least 2-3
weeks) before pushing the final release. This will let some time to the
projects using CLI to try the new version and give their feedback.
Hopefully this will prevent a blocking problem similar to CLI 1.1.
Emmanuel Bourg
Russel Winder a écrit :
Emmanuel,
Is there a way of triggering the CLI 1.2 release process? Given that
there are significant changes over 1.1 and the idea of a 1.3 is not
rejected, I think moving to a 1.2 release sooner rather than later would
be useful. The only threat I can see is if 1.2 has the same blocking
errors as 1.1 compared to 1.2 and I think you believe that the tests are
in place to show that the reported blocking problems of 1.1 are actually
fixed in 1.2-SNAPSHOT.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
