I kinda figured AOP wasn't ready to go GA. ;)
Looks like we have a fairly lengthy dependency chain here, with at least
one project (PojoCache) that AFAIK goes through a QA qual before being
released as a GA. The GA release schedule for all the stuff earlier in
the chain needs to give time for the later stuff to go GA and get
integrated. Sounds like we need a GANTT chart somewhere.
Kabir Khan wrote:
Core aop has dependencies on jboss-reflect and jboss-mdr, which must
go
GA first. Also, there are a few other dependencies from our app server
integration on things like jboss-vfs.
On 27 Aug 2008, at 18:12, Brian Stansberry wrote:
> Moved it. Even if by some chance AOP went GA this afternoon, I don't
> think having PojoCache QA/release a GA and me then properly test it in
> the AS by Friday is realistic.
>
> Is there a JIRA for getting a GA AOP in the AS?
>
> Dimitris Andreadis wrote:
>> Then move it here (or coordinate with Kabir):
>>
https://jira.jboss.org/jira/browse/JBAS-5597
>> Brian Stansberry wrote:
>>> PojoCache can't go GA until AOP does.
>>>
>>> Dimitris Andreadis wrote:
>>>> Friday Aug/29th is the cutoff date for component updates in AS5 CR2:
>>>>
https://jira.jboss.org/jira/browse/JBAS-5122
>>>>
>>>> I expect the following to be completed by then:
>>>>
>>>> - javassist
>>>> - jboss-javaee
>>>> - jbossts
>>>> - pojo/jboss cache
>>>> - ha-client/server
>>>>
>>>> The rest of the modules (ejb3, aspects, mc*) will be tagged at CR
>>>> level when we are done with the tck.
>>>>
>>>> If we are missing something important, speak up now.
>>>>
>>>> Thanks
>>>> /Dimitris
>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>>
>
>
> --
> Brian Stansberry
> Lead, AS Clustering
> JBoss, a division of Red Hat
> brian.stansberry(a)redhat.com
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com