Re: [jboss-as7-dev] Community AS8 Roadmap Proposal

Some comments from me: - This is essentially 18.5 weeks remaining development time (including vacation) for a major release that encompasses non-timeboxable items (e.g. EE7 updates & TCK). Risky IMHO. Looking back to AS history I don't think we ever had such a short cycle for a major release, although I know we want to reduce the scope of major releases going forward. - I think BLOCKER Jiras per milestone should be used. E.g TCK passing items for CR1, EE7 feature completeness for Beta. Tracked items JIRAs should have the same priority with the tracker JIRA (e.g. AS7-6553 for EE) to have a better view of the work that needs to be done. - Overlap with any to-be-committed backportable EAP functionality (e.g. patching) will also drag things back, resource wise. - We need to align work with component leads for any potential updates that will bring in new features. Specify a component freeze date (AS8 Beta, June 11th? CR July 11th?) and try to stick to it. Clarify what exactly that date means because some teams interpret this as a cut off date for a Final component version, some other teams just provide a CR and infinite updates for an unspecified period of time :) Overall the plan is great, we may need to add some more buffers. /D On 27/03/2013 23:57, Brian Stansberry wrote: -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Dimitris Andreadis Software Engineering Manager JBoss Application Server by Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx http://dandreadis.blogspot.com/