here is the precise list of Jira projects we'll migrate: https://github.com/khmarbaise/jira-asf-migration/blob/master/project.list
Regards, Hervé Le jeudi 8 janvier 2015 11:42:54 Stephen Connolly a écrit : > The JIRA projects for the mojo plugins will stay with mojo at codehaus. The > move is only for the ASF hosted code related projects > > On 8 January 2015 at 11:29, Lennart Jörelid <[email protected]> > > wrote: > > Sounds nice. > > > > Presumably, we can retain JIRA admin privileges for the current CodeHaus > > projects after the move to ASF JIRA? > > Or maybe create anew? > > > > I have/require admin privs for the Plugin Projects I'm stewarding on the > > CodeHaus JIRA, but am pretty certain I have no admin privs on the ASF > > JIRA. > > > > 2015-01-08 10:58 GMT+01:00 Stephen Connolly < > > [email protected] > > > > > I got Ben to agree to taking a trial dump this weekend. > > > > > > He will send Hervé the details of the dump. > > > > > > Hervé can then see what is involved in doing the migration. > > > > > > If Hervé feels that the migration is something that can be handled, then > > > > we > > > > > can schedule with Ben to lock all the projects, do the export for real > > > > and > > > > > then Hervé can tidy up the real export. > > > > > > If ASF infra then wants to import each project one at a time after the > > > tidy-up or if infra wants to import all 40-60 projects in one fell > > > > swoop... > > > > > that's infra's call. But the projects on codehaus' JIRA would be locked > > > > to > > > > > prevent changes. Once the import is complete we could then delete the > > > projects from codehaus' JIRA and do the celebratory dance of victory! > > > > > > On 8 January 2015 at 09:52, Stephen Connolly < > > > > > > [email protected]> wrote: > > > > On 8 January 2015 at 06:40, Hervé BOUTEMY <[email protected]> > > > > wrote: > > > >> Le mercredi 7 janvier 2015 08:52:07 Tony Stevenson a écrit : > > > >> > On 7 January 2015 at 07:20, Hervé BOUTEMY <[email protected]> > > > >> > > > >> wrote: > > > >> > > ok > > > >> > > who can prepare a little VM with Jira 6.3.4? Can infra? > > > >> > > > > >> > We cab, but it wont be soon. We are extremely busy right now. I'd > > > >> > imagine it would be a number of weeks before we can look at this > > > >> > for > > > >> > you. > > > >> > > > >> ok, I probably did not ask for the rigth thing: I thing we need a way > > > > to > > > > > >> let > > > >> any Maven developer to have a clean Jira 6.3.4 on his desktop. I > > > >> don't > > > >> know if > > > >> this sould be a puppet script, or a VM image. Or perhaps a procedure. > > > >> I don't know if this is somthing easy for someone used to such > > > >> things. > > > >> > > > >> I intend to try this WE: can I get help on IRC or HipChat? > > > > > > > > Ben is not OK with doing repeated exports... > > > > > > > > I think the most we can get is a trial dump e.g. this weekend and then > > > > if/when we decide to migrate then we lock all the projects, take a > > > > dump > > > > > > and > > > > > > > import them all. > > > > > > > > Ben is not going to be OK with a move each project one at a time. > > > > > > > > Hervé, let me know if you need a trial export to see the size of the > > > > task > > > > > > otherwise I guess we are where we are... unless we want to start > > > > projects > > > > > > clean. > > > > > > > > IOW we could leave the issues in codehaus's JIRA and lock the > > > > projects. > > > > New issues go into ASF JIRA. We triage all the open issues in > > > > codehaus's > > > > > > JIRA and recreate issues on ASF JIRA where we are not rejecting the > > > > codehaus issue. > > > > > > > >> > > and how to get Codehaus content? Any maven dev with knowledge and > > > >> > > > >> karma? > > > >> > > > >> > You will need someone with the Jira Systems Admin privilege to do > > > > the > > > > > >> > export for you. > > > >> > > > > >> > > I'm interested to try the process on MPLUGIN [1] > > > >> > > then be ready for later any Mave developer to do the same for > > > >> > > each > > > > > > and > > > > > > >> > > every Jira project > > > >> > > > > > >> > > notices: > > > >> > > 1. account dedup will have to work when executed multiple times, > > > >> > > > >> since a > > > >> > > > >> > > lot of accounts are shared between Maven Jira projects > > > >> > > > > >> > Understood. > > > >> > > > > >> > > 2. I still didn't understand: will the Jira issue identifiers > > > > change > > > > > >> or > > > >> > > > >> > > not? Will Codehaus MPLUGIN-288 migrate to MPLUGIN-288 in ASF or > > > >> > > is > > > >> > > > >> there > > > >> > > > >> > > a risk that it changes? > > > >> > > > > >> > Assuming that the project keys do not clash with existing ones then > > > >> > that should be ok. Though if you use any method other than the one > > > >> > described by Mark we cannot guarantee the issue ordering will > > > >> > remain > > > >> > intact (i.e. if you scripted it with RPC-XML etc). > > > >> > > > >> great, we clearly need to keep the issues ids > > > >> > > > >> > > Regards, > > > >> > > > > > >> > > Hervé > > > >> > > > >> --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: [email protected] > > > >> For additional commands, e-mail: [email protected] > > > > -- > > > > -- > > +==============================+ > > > > | Bästa hälsningar, > > | [sw. "Best regards"] > > | > > | Lennart Jörelid > > | EAI Architect & Integrator > > | > > | jGuru Europe AB > > | Mölnlycke - Kista > > | > > | Email: [email protected] > > | URL: www.jguru.se > > | Phone > > | (skype): jgurueurope > > | (intl): +46 708 507 603 > > | (domestic): 0708 - 507 603 > > > > +==============================+ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
