Will, I'm fine with using either Jira or Bugzilla -- they both serve our purpose just fine.
- Dan On Fri, 2005-05-13 at 16:30 -0700, Will Glass-Husain wrote: > Ok, let's do it. Geir or Daniel - any response? > > I'd like to use the road map features of JIRA. I was hoping to get a few > more updates in to make it obvious that "yes, there is actual development > activity in Velocity". But at least we're making some progress. > > Note that Shinobu, though a highly active community member, is not (yet) a > committer. > > WILL > > ----- Original Message ----- > From: "Tim Colson (tcolson)" <[EMAIL PROTECTED]> > To: "Velocity Developers List" <velocity-dev@jakarta.apache.org> > Sent: Friday, May 13, 2005 4:22 PM > Subject: Bugzilla -> Jira Request > > > > I started a thread in Velocity-Dev a while ago: > http://www.mail-archive.com/velocity-dev%40jakarta.apache.org/msg11787.h > tml > > Everyone seems to be in agreement. We were waiting on Geir to chime in, > but he hasn't been around the list in a while. All the active committers > were interested in getting off of Bugzilla. > > Back when the thread started, it was just before the Apache "infrathon" > and so I felt it would be better to let things settle down before asking > Infrastructure for the migration. > > I'm going to start assembling the info needed for the request, outlined > here: > > http://wiki.apache.org/general/ApacheBugzillaToJiraMigration > > (BTW -- I had to migrate the Wiki info itself to consolidate the howto's > ;-) > > 1) vote results (nice to have link to mailing list thread) > http://www.mail-archive.com/velocity-dev%40jakarta.apache.org/msg11787.h > tml > Will +1 > Nathan +1 > Shinobu +1 > Geir ? > > (not committers) > Tim +1 > Mike Kienenberger +1 > Konstantin Priblouda +1 > > 2) import bugzilla data > YES > > 3) list of projects (with keys... keys must alphanumeric, first 2 must > be letters, will prefix all issue ids) > > VELOCITY > VELTOOLS > > Note -- we should have "one project per product"... right now I think > these two cover our bases...but if Anakia, for example, were to have > separate releases at some point -- then it would need a new Jira > project. > > > 3a) if multiple projects, if there should be a shared developer group or > each project gets its own group. The developer group will have rights to > edit the issues. > SHARED > > DEVELOPERS GROUP (?): > nbubna > wglass > [EMAIL PROTECTED] > > Others? > > We'll need to provide "JIRA accounts names" -- so if you don't have a > Jira account yet, please create one first. From what I've picked up so > far, you'll want to use the same USERID that you have been committing > code with so Bugzilla will import. > > > 4) email address to send notifications (e.g., your developer email > list). > velocity-dev at jakarta apache org > > 5) email address of an administrator. > this person will be granted JIRA admin access and is responsible for > assigning developers to the project(s) group. > > timcolson @ gmail com -- I will volunteer if no one objects, otherwise > -- somebody needs to sign up for admin stuff. > > > Cheers, > Timo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
