<div dir="ltr">No it has to do with JCP process : <a href="https://www.jcp.org/ja/procedures/jcp2#3.1">https://www.jcp.org/ja/procedures/jcp2#3.1</a><div> and no EDR 1 is not "FINISHED!". Draft is finished but review part will be in 5 days (oct 5) : <a href="https://jcp.org/en/jsr/detail?id=365">https://jcp.org/en/jsr/detail?id=365</a></div><div>There will be a ballot on it starting oct 5.</div><div><br></div><div>This said, you're right, we won't continue on this branch. I said that there's no urgence since we don't have things to commit right away (to my knowledge). It'll change in the coming days.</div><div><br></div><div>Antoine</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">Le mer. 30 sept. 2015 à 09:34, Mark Struberg <<a href="mailto:struberg@yahoo.de">struberg@yahoo.de</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This has nothing to do with the technical ability to find the last commit.<br>
It has purely to do that EDR-1 is FINISHED! This was a nice pun that we do it the wrong way if we continue on this branch…<br>
<br>
I suggest we update the docs in master and pull over the parts we like from EDR-1 and put the rest on the TODO list.<br>
You can also create a new branch for EDR-2 or CDI20-M2 or whatever you like to call it.<br>
<br>
LieGrue,<br>
strub<br>
<br>
> Am 30.09.2015 um 08:38 schrieb Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>>:<br>
><br>
> Still have the 2.0-EDR1 branch.<br>
><br>
> I still don't see the urgence to merge it to master, since we are thinking about reviewing SE boot. But I put 2.0-EDR1 as default branch on Github.<br>
> Honestly I don't think people unable to find last commit in a github repo are the best choice for contributors to the spec ;).<br>
><br>
> Antoine<br>
><br>
><br>
> Le mer. 30 sept. 2015 à 08:29, Mark Struberg <<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>> a écrit :<br>
> Hi Antoine!<br>
><br>
> Side question: what is the state of our GIT repo?<br>
> Where can we find the latest and greatest and a set of things (branches) people are working on.<br>
> Master still seems to not reflect the latest changes. Anyone has an oversight and can fix this please?<br>
><br>
> txs and LieGrue,<br>
> strub<br>
><br>
> > Am 29.09.2015 um 11:36 schrieb Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>>:<br>
> ><br>
> > Hi guys,<br>
> ><br>
> > The blog post is here :<br>
> > <a href="http://www.cdi-spec.org/news/2015/09/29/Second-F2F-meeting/" rel="noreferrer" target="_blank">http://www.cdi-spec.org/news/2015/09/29/Second-F2F-meeting/</a><br>
> ><br>
> > I probably forgot a few stuff (I still have to check in everybody's note) but the main topics are here.<br>
> ><br>
> > As always, feed is welcome and we'll discuss these point sin today's meeting.<br>
> ><br>
> > Antoine<br>
> > _______________________________________________<br>
> > cdi-dev mailing list<br>
> > <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
> ><br>
> > Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
><br>
<br>
</blockquote></div>