At what phase/time-period would tools requirements be discussed ? Last time we said early april but with this schedule is there any room for that ? /max > Due to recent changes in the EAP5 schedule, we have had to > significantly pull in our community dates. The new CR1 and GA dates > are as follows: > > CR1 > --- > Code/Component Freeze : April 20th > Final Console Inclusion : April 22nd > Release : April 27th > > GA > -- > Code/Component Freeze : May 11th > Release : May 25th > > > There is now only 1 goal, and that is meeting our dates with a working > console. > > This also means profile service work is the priority: > https://jira.jboss.org/jira/browse/JBAS-6620 > > All other updates are a nice to have, and if you want them included in > 5.1, they need to be done as early as possible. > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

> I guess, now! We won't be around much before after eclipsecon ;( But lets get it started at least. Any way to get a "restfull"/non-binary-dependent API to a running appserver/profileservice ? or is there a client only api/jar set for profileservice that won't change or at least be backward compatible going forward so tooling won't break when a new AS or EAP release comes out ? Any way for the profileservice to provide deployment-local exception/error/debug info ? /max > > Max Rydahl Andersen wrote: >> >> At what phase/time-period would tools requirements be discussed ? >> >> Last time we said early april but with this schedule is there any >> room for that ? >> >> /max >>> Due to recent changes in the EAP5 schedule, we have had to >>> significantly pull in our community dates. The new CR1 and GA dates >>> are as follows: >>> >>> CR1 >>> --- >>> Code/Component Freeze : April 20th >>> Final Console Inclusion : April 22nd >>> Release : April 27th >>> >>> GA >>> -- >>> Code/Component Freeze : May 11th >>> Release : May 25th >>> >>> >>> There is now only 1 goal, and that is meeting our dates with a >>> working console. >>> >>> This also means profile service work is the priority: >>> https://jira.jboss.org/jira/browse/JBAS-6620 >>> >>> All other updates are a nice to have, and if you want them included >>> in 5.1, they need to be done as early as possible. >>> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development