Odi, One nastiest thing about Bugzilla is its release versioning scheme: the release versions in Bugzilla apply to all components within a project. Since all Commons projects are defined as sub-projects within a project, we cannot have release targets defined specifically for HttpClient. For instance, we can't simply have 2.1 version renamed to 3.0 and 3.0 to 4.0. There may already be other projects using 2.1 tags. We'll have to go through a manual process of reassigning target milestones on all 30 some bug reports. Not to mention asking the Bugzilla admin to create those damn tags for us. JIRA is supposedly free from many of those limitations
Basically my original point was, if we ever wanted to migrate, now would be the right time. I am also quite satisfied with Bugzilla, but do find Bugzilla's versioning scheme constraining. Oleg -----Original Message----- From: Ortwin Glück [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 13:41 To: Commons HttpClient Project Subject: Re: JIRA vs Bugzilla issue Oleg Kalnichevski wrote: > Folks, > What say you, do we migrate HttpClient issue tracking to JIRA or do we > stay with Bugzilla? Please let me know your opinion. > > Oleg Sorry, I have not had the time to take a look at JIRA and I don't know that product at all. All I can say is that I am quite familiar and happy with Bugzilla and I don't miss anything currently. Odi --------------------------------------------------------------------- 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]
