Hi.
On Tue, 7 Aug 2018 21:44:05 -0400, Rob Tompkins wrote:
On Aug 7, 2018, at 9:25 PM, Gilles <gil...@harfang.homelinux.org>
wrote:
On Tue, 7 Aug 2018 18:48:40 -0600, Gary Gregory wrote:
Hi All,
Let me rephrase the question: Is the change part of what RNG
considers its
public API?
The first Clirr error was settled, as noted in the JIRA ticket.
If yes, the we must not break BC in a minor release.
1.1 should be a drop in replacement to 1.0 and not cause a runtime
error.
The second error must then the fixed (by allowing the user to
shoot himself in the foot as noted below).
I apologize to Rob for wasting another RC...
No apologies necessary. In the same light I would want to apologize
for moving slowly to the 1.1-RC1. :-)
Also, the release plugin has made it way more reasonable to cut an
RC.
What’s the plan here? Change the access modifier and go for RC7?
Based on the conversation I’m feeling like my vote would be in the
-0.5 to -1 area for RC6.
Clirr issue fixed (in "master" and "1.1" branches).
Thanks to Gary for spotting it and thanks in advance to Rob for RC7...
Gilles
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
