Request filed: http://issues.apache.org/jira/browse/INFRA-763
Oleg On Sun, 2006-03-19 at 20:37 +0100, Oleg Kalnichevski wrote: > Folks, > > While reviewing the Bugzilla to Jira migration procedure [1] I learned > that Jira had been designed to require one JIRA project for every > versioned product, which was a bit of a surprise to me. If we just > migrated HttpClient from Bugzilla to Jira we would end up with one > versioned project and would not be able to have different release > versions and target milestones for different project modules. This is > probably not what we want. > > It looks like we have got to have a separate Jira project per module > with a different release cycle: > > HttpComponents HttpCore (4.x) > HttpComponents HttpAsync (x.x) > HttpComponents HttpNIO(x.x) > Commons HttpClient (3.x) > and so on > > Taking all this into account I believe we might be better off at this > point setting up a brand new Jira projects for [HttpCore], [HttpNIO] and > [HttpAsync], getting some first hand experience with Jira, and > considering migrating HttpClient from Bugzilla at some point in the > future provided we are reasonably satisfied with Jira. > > I will manually migrate [HttpCore] related issue reports from Bugzilla > to Jira. There are probably no more than 5 or 6 of those in total > > What do you think? > > Oleg > > [1] http://wiki.apache.org/general/ApacheBugzillaToJiraMigration > > > --------------------------------------------------------------------- > 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]
