The main issue for improving progress is a more uniform application of resources. If every lead is responsible for getting 1-2 production release issues resolved per week, we would have a better progression to a release as well as better understanding of what issues should be delayed due to needing to be broken up better, reduced in priority, etc.
> -----Original Message----- > From: Andy Miller > Sent: Monday, April 17, 2006 7:25 AM > To: Dimitris Andreadis; Adrian Brock; Scott M Stark; Ivelin Ivanov > Cc: jboss-development > Subject: RE: Improving the JBAS JIRA handling process > > Dimitris, > > I completely agree with all of those. Have you started > the discussion on the components leads yet? If not, let's > get that discussion started. I think that is the first thing > that needs to get straightened out. After that, we can start > to put some processes in place to make things smoother. Some > components are also in transistion, such as transactions and > JMS. So, we need to have an understanding that the > components leads in JBoss AS 5 will be different then they > are in JBoss AS 4.0.x or 3.2.x. > > Andy > > > -----Original Message----- > From: Dimitris Andreadis > Sent: Mon 4/17/2006 4:41 AM > To: Andy Miller; Adrian Brock; Scott M Stark; Ivelin Ivanov > Cc: jboss-development > Subject: Improving the JBAS JIRA handling process > > > Some of the problems we have now with our JIRA case handling are: > > - entered cases often have no component assigned, thus nobody > looks at them > - cases with a component are not qualified at all; we have > cases that date back to the sourceforge days > - cases having more than one assigned components may cause > confusion as to who's handling them > > In addition, the current break-out of the server subsystems > into component (shown in the bottom) maybe a bit outdated. > > I believe we need to > > A) clarify/document the JIRA case handling process > B) revise/validate/update the component list and the leads > C) throw in ideas for improving our case handling to make it > more effective and timely. > > Your input is welcome > > Thanks > /Dimitris > > > Build System (Lead: Scott M Stark) > Clustering (Lead: Scott M Stark) > CMP service (Lead: Alexey Loubyansky) > Deployment Service (Lead: Dimitris Andreadis) Documentation > (Lead: Norman Richards) EJBs (Lead: Scott M Stark) Hibernate > service (Lead: Steve Ebersole) IIOP service (Lead: Dimitris > Andreadis) Installer (Lead: Scott M Stark) JAXR service > (Lead: Anil Saldhana) JBoss Cache service (Lead: Bela Ban) > JCA service (Lead: Adrian Brock) JGroups service (Lead: Bela > Ban) JMS service (Lead: Adrian Brock) JMX (Lead: Scott M > Stark) Logging (Lead: Scott M Stark) Management Service > (Lead: Dimitris Andreadis) MicroContainer bus (Lead: Adrian > Brock) Naming (Lead: Scott M Stark) Other Remoting (Lead: Tom > Elrod) Security (Lead: Scott M Stark) System Service (Lead: > Dimitris Andreadis) Test Suite (Lead: Scott M Stark) > Transaction Manager service (Lead: Adrian Brock) Web (Tomcat) > service (Lead: Remy Maucherat) Web Services service (Lead: > Thomas Diesler) XML Service (Lead: Alexey Loubyansky) > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
