Gilles: I can see you are frustrated by the late comments and opinions when
the code has been sitting in the repo for all to see. I hope we can resolve
all of this amicably.
All: We have only one shot at 1.0, this will set the tone for a 1.x line.
If things change/mature/break enough then it becomes 2.0, but if it happens
too soon, then it might give the impression that our process is not mature.
It seems we have a difference of opinion as to whether the current code is
ready for 1.0.
Now that we have both sides engaged in this discussion, we can try to
resolve these differences in email agreements or in code changes. Maybe the
-1 party could create Jiras to address specific issues, or should all this
happen on the ML?
>From my experience, when I or someone finds any problem with an RC I
rolled, I sigh, cancel, and redo; but not before complaining to myself that
if there where not 50 steps to do a release, it would be less of a pain.
On Sat, Sep 17, 2016 at 8:28 AM, Emmanuel Bourg <ebo...@apache.org> wrote:
> Le 17/09/2016 à 13:34, Gilles a écrit :
> > Your behaviour is in blatant contradiction with the Apache
> > motto, and this project's chair mantra (RERO), which is
> > truly ignored by the facts.
> RERO isn't the Apache motto (and I'm not opposed to a release, I'm
> opposed to declaring the current code as final and well polished).
> Apache is actually focused on consensus and collaborative work, your
> behavior goes against that.
> >  Work with me towards modularity.
> No thanks, I'm not interested in working with someone not open to
> others' views. If even formatting a table properly is an issue for you
> there is little I can do.
> Emmanuel Bourg
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>