Could the breaking changes be documented together in one ticket so we can review that and provide this ticket as a single point of documentation? An explanation of why it is OK to break BC would be helpful and reassuring.
2c, Gary On Mon, Oct 3, 2016 at 3:05 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > Hi all, > > JEXL is ready for a new release, before creating the artifacts and > starting the vote I'd like to ensure there is a consensus on the API > changes. The version 3.1 has 3 incompatible changes that shouldn't have > any impact on the users [1]. > > I plan to start the vote at the end of the week. > > Thank you for your reviews, > > Emmanuel Bourg > > [1] http://people.apache.org/~ebourg/jexl/site/clirr-report.html > > --------------------------------------------------------------------- > 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 <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
