[cdi-dev] CDi 1.1.1 MR

Antoine Sabot-Durand antoine.sabotdurand at gmail.com
Wed Nov 13 11:54:51 EST 2013


Hi all,

Walking thru most of « clarification » ticket I built my whish list for MR. I know it’s quite long and I don’t ticket could resolved for 1.1.1 (not impossible but quite hard), but I think we need at least to give a status on these open tickets :

CDI-77	Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans
CDI-220	behaviour of CDI bean @Specializes session bean is undefined
CDI-280	clarify usage of 'bean' term usage in the spec
CDI-401	Clarify the meaning of "bean class local view"
CDI-395	Public fields in extensions should not be allowed
CDI-392	Clarify when the operations of BeanManager can be called
CDI-382	Clarify interceptors are not associated with the result of a producer method/field
CDI-320	Clarify whether ProcessAnnotatedType should be fired for annotations*
CDI-318	@WithAnnotations types can appear on any supertype
CDI-405	Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1
CDI-397	Clarify Section 6.6.3 regarding singletons
CDI-372	clarify behaviour of implicit bean archive
CDI-381	Additional implementations of Request Context
CDI-380	Clarify SessionScoped
CDI-379	Clarify life cycle of RequestScoped

And my bonus one (yes I hesitated on this but IMO we really should statute on it)

CDI-370 Expand @RequestScoped and @SessionScoped to account for WebSocket



Antoine Sabot-Durand /@antoine_sd
———————————————
CDI co-spec lead
CDI eco-system development
Agorava tech lead

Le 8 nov. 2013 à 18:34, Pete Muir <pmuir at redhat.com> a écrit :

> +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
> 




More information about the cdi-dev mailing list