@Eric, The Archiva import is more simple as it's only one project compared to all Maven projects. But good to know what is your asf jira id. (very simple if it's the same)
On 3 April 2015 at 18:42, Eric Barboni <[email protected]> wrote: > Hi Hervé > should the same process be done for archiva continuum and groovy ? > > Regards > Eric > Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY <[email protected]> > a écrit: > > > Hi Maven devs, > > > > After Jira migration to ASF, we'll need to create groups to give required > > privileged access to issues to the team. > > > > We need to know the Jira username of everybody, which unfortunately is > not > > required to be the same as your Apache id. > > I started the list in http://svn.apache.org/r1670998 > > > > Please update your Jira username. > > > > Thank you > > > > Hervé > > > > Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : > > > The migration will start in 12h: every Jira project at Codehaus to be> > migrated to ASF will be marked read-only > > > > > > Remember to check your Jira account email settings both at Codehaus > and ASF > > > if you want to be sure of the result at ASF. > > > And everything is tracked at > > > https://issues.apache.org/jira/browse/INFRA-9116 > > > > > > -The Apache Maven team > > > > > > Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : > > > > Hi, > > > > > > > > Schedule confirmed: > > > > 20150403-2000 UTC => projects freeze in Codehaus > > > > 20150405 => projects available in ASF > > > > > > > > Don't forget to check account emails if you already have an account > at ASF > > > > > > > > -The Apache Maven team > > > > > > > > Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : > > > > > Hi, > > > > > > > > > > As announced in our quarterly report from january, we were > studying Jira > > > > > migration from Codehaus to Apache: the migration will happen > during the > > > > > week- end of April 4th. > > > > > > > > > > We'll create the exact same Jira projects at ASF than what we > have at > > > > > Codehaus, copy the whole content and mark Codehaus read-only. > > > > > See https://issues.apache.org/jira/browse/INFRA-9116 for exact > list. > > > > > > > > > > For example, it was done a few years ago with (near empty) MPOM, > which > > > > > was > > > > > moved from http://jira.codehaus.org/browse/MPOM to > > > > > https://issues.apache.org/jira/browse/MPOM > > > > > > > > > > > > > > > How will username migration from Codehaus to ASF happen? > > > > > > > > > > When migrating existing content, user accounts will be migrated too > > > > > (that's > > > > > the way Jira works). > > > > > > > > > > To avoid creating accounts that already exist at Apache, matching > will > > > > > be > > > > > done on account's e-mail address. The mapping will look something > like: > > > > > > > > > > for each e-mail/username pair in the Codehaus content > > > > > > > > > > if the email is associated with a user in the ASF Jira instance, > > reuse: > > > > > update the username from imported content to the ASF username> > > > > > > > > else we'll create a new account in the ASF Jira instance: > > > > > if the username already exists in the ASF Jira instance > (another > > > > > email) > > > > > > > > > > update the imported username to append -[SUFFIX] to the end> > > > > > > > > else > > > > > > > > > > use the imported username/email as is > > > > > > > > > > The exact [SUFFIX] still needs to be defined. > > > > > > > > > > If you want to be sure of your username at Apache Jira, please > take a > > > > > look > > > > > at your e-mail at Codehaus and check that it matches the e-mail at > your > > > > > Apache Jira account. > > > > > > > > > > > > > > > If you have any question, don't hesitate to ask. > > > > > > > > > > We'll keep you informed as the operation is planned more in > details. > > > > > > > > > > -The Apache Maven team > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > --------------------------------------------------------------------- > > 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] > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
