Hi all,All the releases are done and I've just sent the 2.0.0.Final versions of the spec artifacts to the JCP.They should be available for download from the jcp.org JSR page within the next few days. We'll push out announcements on beanvalidation.org and the Hibernate blog (for the RI) on Monday (as announcements on Friday tend to get less exposure).Once the Final artifacts are on jcp.org, the Expert Group's work on Bean Validation 2.0 is complete, and as per the JCP rules it officially disbands. I.e. we're done!Thanks a lot to everyone for their hard work and contributions to this JSR. Your efforts are truly appreciated. It has been a pleasure for me to work with all of you on this JSR. I especially enjoyed the open, friendly and productive style of collaboration. I think we can be very proud on what we achieved -- it's a nice package of very useful functionality we've added to BV.So what's next? Let's all relax and think about something other than Bean Validation for a while :)After that, I certainly can envision a future BV 2.1, addressing some of the things we didn't get to work on this time around, e.g. better support for fully self-contained constraint libraries, an API for constraint declaration (using Lambdas?) or perhaps a reactive flavour of the API which could be useful for UI-centric use cases. Also support for Java 9 modules and Java 10 value types will be interesting.But let's talk about the details at another time ;)Thanks again and all the best,--Gunnar2017-08-03 20:10 GMT+02:00 Christian Kaltepoth <christian@kaltepoth.de>:Awesome! Thanks everyone!--2017-08-03 18:59 GMT+02:00 Emmanuel Bernard <emmanuel@hibernate.org>:Champagne!On 3 Aug 2017, at 12:50, Gunnar Morling <gunnar@hibernate.org> wrote:______________________________Hi all,I'm very happy to report that we've passed Final Approval Ballot for BV 2.0, with all 25 JCP EC members voting with Yes [1]!The next step will be to do the final release of the spec, API and the TCK (i.e. version 2.0.0.Final). The spec and the API are re-tagged releases of CR3. The final release of the TCK contains one actual change, as we spotted a flawed TCK test which got fixed since the CR3 [2].These releases will happen today, followed by the Final RI release tomorrow.Cheers,--Gunnar_________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev