This is not a vote BTW On 1 June 2011 11:25, Mark Struberg <[email protected]> wrote: > +1 > > the problem with cross referencing already exists on the other side too. I > e.g. cannot link from a WAGON-329 (hosted at codehaus atm) to FTPSERVER-413 > (hosted at apache). > > LieGrue, > strub > > --- On Wed, 6/1/11, Stephen Connolly <[email protected]> wrote: > >> From: Stephen Connolly <[email protected]> >> Subject: [RFC] Migrating Maven JIRA from jira.codehaus.org to >> issues.apache.org >> To: [email protected], "Maven Developers List" <[email protected]> >> Date: Wednesday, June 1, 2011, 10:21 AM >> REQUEST FOR COMMENTS: Potential >> migration of Maven's JIRA from >> jira.codehaus.org to issues.apache.org >> >> Just wondering now that codehaus and apache are on nearly >> similar >> versions (4.1.2 and 4.2.4 respectively) what would be >> involved. >> >> Ben@codehaus can give us a 4.1.2 dump of the entire >> codehaus jira and >> we'd just have to cull out the non-maven projects (easier >> way than any >> others is what Ben thinks as most of the projects are Maven >> based >> projects) >> >> On the Infra side, would this be the easiest way to pull >> the issues in? >> >> What do people think in general? >> >> +1's: >> * We'd be fully on Apache controlled hardware >> >> -1's: >> * Since a lot of the issues end up being actually issues >> in a lower >> layer (most of which if not ASF hosted live/lived @ >> codehaus) or an >> upper layer (i.e. one of the mojo plugins) we'd loose the >> ability to >> move those issues to the correct project and instead we'd >> have to >> create a new tracking issue on the root cause project's >> jira >> * What we have works, if it ain't broke don't fix it >> >> Once we have enough comments/feedback (I'm willing to give >> a week or >> two), I'll put the options to the Maven PMC who will >> ultimately EITHER >> make a decision OR delegate making a decision to all the >> Maven >> committers. >> >> -Stephen >> >> --------------------------------------------------------------------- >> 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]
