[cdi-dev] CDi 1.1.1 MR

[Pete Muir]

+1

A MR can run for 1,2, or 3 months. We should choose one, I suggest 2 months, and we submit for the MR on 1st Dec (meaning it closes 1st Feb).

On 8 Nov 2013, at 16:51, Antoine Sabot-Durand <antoine.sabotdurand at gmail.com> wrote:

> I created a new version in JIRA : 1.1.1 (Proposed) : https://issues.jboss.org/browse/CDI/fixforversion/12323655
> 
> I propose we close this list the week after Devoxx (one week from now). We could have a meeting (Hangout) on the 18th, then let us a few more days and close the list on the 21st.
> It gives us one week to complete this list.
> 
> What do you think ? 
> 
> Antoine
> 
> Le 8 nov. 2013 à 09:39, Antoine Sabot-Durand <antoine.sabotdurand at gmail.com> a écrit :
> 
>> For the record I report Jozef priority list here (better thread name)
>> Great to see CDI-377 on the top of your list ;
>> 
>>> https://issues.jboss.org/browse/CDI-377
>>> https://issues.jboss.org/browse/CDI-389
>>> https://issues.jboss.org/browse/CDI-404
>>> and possibly
>>> https://issues.jboss.org/browse/CDI-406
>> 
>> 
>> 
>> 
>> Antoine
>> 
>> Antoine Sabot-Durand
>> 
>> Le 7 nov. 2013 à 16:40, Antoine Sabot-Durand <antoine.sabotdurand at gmail.com> a écrit :
>> 
>>> Hi all
>>> 
>>> Maintenance Release is indeed quite critical. As stated by Pete we should have a tight scope but address significant issue or needed clarification. Some interoperability issues should also IMO be studied to see if we can address them in 1.1.1 (the https://issues.jboss.org/browse/CDI-377 comes to my mind).
>>> As we are a bit late on this MR, I propose to try to have it time boxed (deliver early, deliver often) to show we’re still alive ;) .
>>> My main idea is to prioritize issues, give us a deadline (not too straight) and do the maximum in this time frame.
>>> 
>>> WDYT
>>> 
>>> Antoine
>> 
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev