I believe that bringing issues in an older version to the current version will proceed smoothly. For work, we have been using Scarab since b7. Everytime we upgrade we run the various upgrade scripts and the issues look alright at the end.
Eric -----Original Message----- From: John McNally [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 18, 2002 7:41 PM To: Turbine Developers List Subject: RE: [Proposal - Vote required] Issue tracking I agree with Stephen's comments. Importing issues is not yet done, though it might be soon. I don't know how well it might work with issues exported from an an older beta though. I don't expect that jon will be writing any transformations. As far as import of bugzilla issues, i think that will have to be a manual process. The dtd that ships with bugzilla does not correspond to the actual xml output which varies from version to version. john mcnally On Tue, 2002-09-17 at 08:38, Stephen Haberman wrote: > > jira.werken.com > > * Proposed strategy: Keep using for present. Jason and co. to > determine if > > they want to move to Scarab, when this might occur, etc. > > +1 > > > issues.apache.org/scarab > > * 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?). > > +1 > > > * 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. > > -1, it might be a pain at first, but I think they would come to enjoy a > maintained, up to date version of Scarab. > > > 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. > > +0, I'm all for moving the bugzilla stuff to the werken Scarab install, > but it's more a call of the turbine-2/fulcrum committers. > > > scarab.werken.com > > * Global > Turbine > JCS > > -0, I don't think JCS needs to be cast under Turbine. That's how it was > snuck into Apache, but other than that, it's not really Turbine related. > > > * [Global > Turbine > Stratum]? > > -0 > > > * [Global > Turbine > Flux]? > > -0 unless people are actually using and actively developing Flux? > > > * Reserved: [Global > Turbine > Maven] > > -0, I think the Maven people would like Global > Maven instead; some of > them are pretty focused on moving into their own spotlight instead of > hiding under Turbine (which is understandable) > > > * Reserved: [Global > Turbine > OJB] > > -0, same thing, Global -> OJB I think is better. > > > * Update the issue tracking references (in project.xml) for the > project > > sites to direct to http://scarab.werken.com/issues > > +1 > > > 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. > > +1 > > Thanks for stepping up to do this, Scott. I agree that it needs to be > more organized. > > - Stephen > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
