[Please excuse the cross-post. As I don't subscribe to turbine-maven-dev, turbine-jcs-dev or ojb-dev I expect my post won't make it to these groups. Can someone that subscribes to these lists please forward them a copy of this post to ensure that all turbine projects get the opportunity to vote on this proposal.] [Please reply only to [EMAIL PROTECTED]]
I would like if possible to tidy up the issue tracking systems used by the turbine projects. Projects that fall under the turbine umbrella currently have access to multiple issue tracking systems (some non-turbine projects are referred to in passing). With the aim of eventually consolidating all turbine projects onto a single issue tracking system I would like to propose the following strategies be adopted. The short term goal is to minimise the possibility of the wrong system being used to enter issues (at the very least we need the projects themselves to point to the issue tracking system that is actually in use - this is not currently the case). Note that for turbine based projects there appears to be a strong preference for the use of Scarab (from http://scarab.tigris.org). Refer to http://archives.apache.org/eyebrowse/BrowseList?listId=99&by=thread&from=230 286 for some recent discussion on this subject. The issue tracking systems currently in use by turbine projects (in no particular order) are: jira.werken.com - maven: 105 issues in total, 62 closed/resolved, 42 open - jelly (non-turbine): 7 issues in total, 3 fixed & 4 unresolved * Proposed strategy: Keep using for present. Jason and co. to determine if they want to move to Scarab, when this might occur, etc. issues.apache.org/scarab * Note: This is an un-maintained install of Scarab. My understanding is that the scarab.werken.com instance was created because it was difficult to gain the necessary access to install and maintain an instance on the apache server. - Global > Jakarta (non-turbine): 2 issues - look like garbage. * Proposed strategy: Kill the Global > Jakarta module. - Global > XML (non-turbine): no issues * Proposed strategy: Kill the Global > XML module. - XML > Forrest (non-turbine): no issues * Proposed strategy: Kill the XML > Forrest module - Jakarta > Turbine: 1 issue entered 2002-09-09 * Proposed strategy: Move this one issue to scarab.werken.com and kill the Jakarta > Turbine module. - Jakarta > Turbine > Maven: 4 issues in total, all open. * Proposed strategy: Kill the Jakarta > Turbine > Maven module on the assumption that all relevant issues are up on jira.werken.com. - Jakarta > Turbine > OJB: 34 issues, all open. * Proposed strategy: This is the messy one. Inform the OJB guys that the scarab install they are using is un-maintained and offer to set up a module for them on scarab.werken.com. If someone has the knowledge necessary to transfer the existing issues over, this would probably be welcome (I know Scarab can export issues, but does it have an import facility yet?). * Proposed strategy: issues.apache.org/scarab will exist solely for use by the OJB guys. If they decide to move over to scarab.werken.com then this scarab instance should be decommissioned. issues.apache.org/bugzilla - turbine: 33 open issues * Proposed strategy: If possible, remove ability to create new turbine issues. If someone has the knowledge necessary to transfer the existing issues over to scarab.werken.com, this would probably be welcome, alternatively the existing issues will be transferred manually over to the appropriate modules on scarab.werken.com. Discretion will be used to determine whether or not an issue will be transferred, more specifically, issues that relate to Maven and some of the issues that are no longer believed to exist will not be transferred. scarab.werken.com * Note: John McNally and Stephen Haberman have volunteered to maintain this Scarab instance. * Note: There is an implicit assumption here that Werken are happy to accommodate the other turbine projects in addition to torque. Perhaps someone closer to Werken can confirm that this is the case and to pass on the the appreciation of the turbine community. - Global > Torque: 27 issues, mostly open. * Proposed strategy: * Establish modules for the remaining turbine projects (with the exception of Maven and OJB). Suggested modules (someone more familiar with Scarab please jump in and correct this if it is not correct): * Global * Global > Turbine * Global > Turbine > Torque [Can the existing Global > Torque module be moved to this?] * Global > Turbine > Turbine-2 * Global > Turbine > Turbine-3 * Global > Turbine > Fulcrum * Global > Turbine > Site * Global > Turbine > TDK * Global > Turbine > JCS * [Global > Turbine > Stratum]? * [Global > Turbine > Flux]? * Reserved: [Global > Turbine > Maven] * Reserved: [Global > Turbine > OJB] * Update the issue tracking references (in project.xml) for the project sites to direct to http://scarab.werken.com/issues Other requirements: * Proposed strategy: The page at http://issues.apache.org/ should be updated to de-emphasise the apache scarab install (was it really going to replace bugzilla for all projects?) and to include reference to the scarab.werken.com instance for turbine project issues. I am willing to co-ordinate the above proposal. For now, please vote and comment. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
