Sounds good to me.<br><br>Do we already have this somewhere:<br><br>> JSR Implementations (1.4): Maintenance Leads must provide a complete <div>> list of all implementations of the specification which have been certified as </div>
<div>> compatible and have been publicly or commercially released. This list must </div><div>> be provided at least quarterly, to be published publicly on <a href="http://jcp.org">jcp.org</a>.<br></div><div><br></div>
<div>--Gunnar</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/22 Gerhard Petracek <span dir="ltr"><<a href="mailto:gerhard.petracek@gmail.com" target="_blank">gerhard.petracek@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 for being as open as we can!<div><br></div><div>regards,</div><div>gerhard<div><div class="h5"><br><br><br><br><div class="gmail_quote">
2012/11/22 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I was pretty sure I sent such an email a while back but I can't find it.<br>
<br>
I would like to move our spec to the latest and more opened JCP rules aka 2.9. I am almost certain that we do comply with it and that we even go further than what is expected of us. For your info rules 2.8 force things like publicly visible and archived communication. We currently are under the JCP 2.7 rules.<br>
<br>
Here is a list of changes <a href="http://jcp.org/en/resources/2.8" target="_blank">http://jcp.org/en/resources/2.8</a><br>
Here is how to migrate <a href="http://jcp.org/en/resources/change_jcp_version" target="_blank">http://jcp.org/en/resources/change_jcp_version</a><br>
<br>
Please speak up if you don't want the spec to move to the new rules. Otherwise I will proceed next week after turkeys have been thoroughly digested by our USA reps :)<br>
<br>
Emmanuel<br>
_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
<br></blockquote></div><br></div>