<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi all,</div><div><br></div><div><br></div><div>Sorry for the delay.</div><div>You’ll find the 11/18/2013 meeting notes here [1]. The asciidoc source below :</div><div><br></div><div><div>= CDI EG meeting 11/18/2013 notes on CDI 1.1.1 MR</div><div><br></div><div>The goal of this 1st meeting was to organize the MR launching, and start discussing its content</div><div>The following people assisted this meeting :</div><div><br></div><div>* Pete Muir (pm)</div><div>* Mark Struberg (ms)</div><div>* Jozef Hartinger (jh)</div><div>* Joseph Bergmark (jb)</div><div>* Arne Limburg (al)</div><div>* Antoine Sabot-Durand (asd)</div><div><br></div><div>== Proposed Agenda </div><div><br></div><div>The following agenda was proposed by *asd*</div><div><br></div><div>1. MR proposed roadmap </div><div>2. Content of the proposed list </div><div>3. Try to have a 1st decision on big tickets (tickets with great impact on implementation or spec) </div><div> * CDI-377 : automatic JSR-330 annotation processing problematic </div><div> * CDI-370 : Expand @RequestScoped and @SessionScoped to account for WebSocket </div><div> * others </div><div><br></div><div>== Proposed Roadmap</div><div>As we should run the MR in 60 days and that we cannot change its content after its start we proposed the following roadmap</div><div><br></div><div>* 16th Dec - list of issues complete</div><div>* 6th Jan - Maintenance review starts</div><div>* 7th March - Maintenance review ends</div><div>* 21st March - Maintenance ballot ends</div><div><br></div><div>This roadmap integrates the holidays constraints as well. It'll be confirmed after the meeting *pm* and *asd* will have with the JCP on 11/26 </div><div><br></div><div>== Content of the proposed list</div><div><br></div><div>*asd* stressed on the fact that the long proposed list won't probably fit in the MR but that would be nice to provide them a status.</div><div>We decided to deal the most important ticket first. </div><div><br></div><div>== list of tickets</div><div><br></div><div>=== <a href="https://issues.jboss.org/browse/CDI-377[CDI-377">https://issues.jboss.org/browse/CDI-377[CDI-377</a> : automatic JSR-330 annotation processing problematic]</div><div>All the participant agreed that this ticket could be quite tricky. 2 scenario for solving it</div><div><br></div><div>* Having an umbrella scanning mechanism : beyond CDI and off course the MR.*pm* took note of escalate this need to the JCP</div><div>* in the meantime could investigate an exclusion in beans.xml. this solution is to be explored and if we have an agreement we could provide a fix in MR scope</div><div> </div><div>=== <a href="https://issues.jboss.org/browse/CDI-370[CDI-370">https://issues.jboss.org/browse/CDI-370[CDI-370</a> : Expand @RequestScoped and @SessionScoped to account for WebSocket]</div><div>A tricky issue as well. No one in the EG has a sufficient knowloedge of websocket sepc to statute ont in so *pm* propose to ask help to *Matthias Wessendorf* </div><div><br></div><div>Other tickets related to `@RequestScoped` clarification </div><div><br></div><div>* <a href="https://issues.jboss.org/browse/CDI-379[CDI-379">https://issues.jboss.org/browse/CDI-379[CDI-379</a> Clarify life cycle of RequestScoped]</div><div>* <a href="https://issues.jboss.org/browse/CDI-381[CDI-381">https://issues.jboss.org/browse/CDI-381[CDI-381</a> and other request scope related ticket]</div><div>* <a href="https://issues.jboss.org/browse/CDI-406[CDI-406">https://issues.jboss.org/browse/CDI-406[CDI-406</a> Make stereotypes bean defining annotations]</div><div><br></div></div><div><br></div><div>[1] <a href="http://docgist.nawroth.se/?dropbox-2898173%2Fcdi%2520eg%2Fmeetings%2F2013-11-18_EG-meeting.asc">http://docgist.nawroth.se/?dropbox-2898173%2Fcdi%2520eg%2Fmeetings%2F2013-11-18_EG-meeting.asc</a></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Antoine Sabot-Durand /@antoine_sd<br>———————————————<br></div><div>CDI co-spec lead<br>CDI eco-system development<br></div><div>Agorava tech lead</div></div>
</div>
<br></body></html>