Chris, There has been no update on the JIRA migration.
https://issues.apache.org/jira/browse/INFRA-10144 Can you please check with Gavin? Thanks, Thomas On Fri, Sep 18, 2015 at 8:12 PM, Chris Nauroth <[email protected]> wrote: > I also noticed today that the INFRA-10145 issue seemed to vanish. This > was surprising to me, as I thought issues generally don't ever completely > delete. > > There is still the master jira for tracking Apex infrastructure issues, > and that's INFRA-10144. I used that one to ask Gavin for an update on the > JIRA migration earlier today. I'll attach the spreadsheet there too. > > --Chris Nauroth > > From: Thomas Weise <[email protected]> > Date: Friday, September 18, 2015 at 5:55 PM > To: "[email protected]" <[email protected]>, > Chris Nauroth <[email protected]> > > Subject: Re: Apex ASF JIRA Migration > > Chris, > > We are done collecting the mapping info. I'm attaching the snapshot as > CSV, or use this link: > > > https://docs.google.com/spreadsheets/d/1Zq6eK-ZpJv_HNzQl-OffAWW2Mf7iVoFOfT-bYtu6Q2E/edit#gid=0 > > I cannot access the INFRA ticket, otherwise I would have attached it there: > > https://issues.apache.org/jira/browse/INFRA-10145 > > Can you please update it or notify Gavin? > > It would also be great to notify this list once the migration takes place > so folks stop making changes at the source. > > Thanks, > Thomas > > > On Wed, Sep 16, 2015 at 8:07 AM, Thomas Weise <[email protected]> > wrote: > >> Thanks to those of you who added their ASF JIRA username. Friendly >> reminder to the rest. >> >> Let's give it one more day and then hand the mapping over to the folks >> working on the migration. >> >> Thomas >> >> >> On Sun, Sep 13, 2015 at 6:19 PM, Thomas Weise <[email protected]> >> wrote: >> >>> The Malhar JIRA (https://malhar.atlassian.net/) will soon be migrated >>> to ASF. In a best effort to preserve history as closely as possible, we ask >>> that you provide your ASF JIRA username in the following spreadsheet: >>> >>> >>> https://docs.google.com/spreadsheets/d/1Zq6eK-ZpJv_HNzQl-OffAWW2Mf7iVoFOfT-bYtu6Q2E/edit?usp=sharing >>> >>> This information will be used to map the username fields on existing >>> tickets as part of the migration process. If you don't have a login yet, >>> you can sign up at: >>> >>> https://issues.apache.org/jira/secure/Dashboard.jspa >>> >>> Thanks, >>> Thomas >>> >>> >>> ---------- Forwarded message ---------- >>> From: Thomas Weise <[email protected]> >>> Date: Sun, Sep 13, 2015 at 5:43 PM >>> Subject: Re: Apex ASF JIRA Migration >>> To: [email protected] >>> >>> >>> Here is the mapping to enter your ASF JIRA username ( >>> https://issues.apache.org/ - please sign up if you don't have one yet): >>> >>> >>> https://docs.google.com/spreadsheets/d/1Zq6eK-ZpJv_HNzQl-OffAWW2Mf7iVoFOfT-bYtu6Q2E/edit?usp=sharing >>> >>> I will also send an email to the address on record. >>> >>> Thanks, >>> Thomas >>> >>> >>> On Sun, Sep 13, 2015 at 3:55 PM, Amol Kekre <[email protected]> >>> wrote: >>> >>>> Chris, >>>> This is indeed great news. >>>> >>>> Thks, >>>> Amol >>>> >>>> >>>> On Sun, Sep 13, 2015 at 3:13 PM, Thomas Weise <[email protected]> >>>> wrote: >>>> >>>> > Thanks Chris, this is great news. I will work on putting together a >>>> mapping >>>> > spreadsheet. >>>> > >>>> > Thomas >>>> > >>>> > On Sun, Sep 13, 2015 at 3:11 PM, Chris Nauroth < >>>> [email protected]> >>>> > wrote: >>>> > >>>> > > Good news! Gavin has figured out a simpler import process that >>>> won't >>>> > > require the mass upgrade of JIRA. >>>> > > >>>> > > Gavin needs help with defining a mapping from the usernames in the >>>> > > Atlassian instance to the usernames in the Apache instance. I've >>>> pasted >>>> > > more details from Gavin's last update on INFRA-10145 below. >>>> > > >>>> > > Amol, would you be able to help gather this information and post it >>>> on >>>> > > INFRA-10145 for Gavin? I expect you or one of your peers will be >>>> able to >>>> > > do the most thorough job of this, because you have direct daily >>>> contact >>>> > > with many of the initial contributors. Thank you. >>>> > > >>>> > > --Chris Nauroth >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > --- >>>> > > >>>> > > Ok [~cnauroth] I've had a good look around and I'm confident I can >>>> do the >>>> > > imports without the need to upgrade our Jira instance. >>>> > > >>>> > > What I need from you is help with user mappings. >>>> > > >>>> > > For instance you have a user called 'nick' but that username >>>> belongs to a >>>> > > different user in our jira. So, does your 'nick' have an existing >>>> > > different username in our Jira? If not can he create one. I'd like >>>> this >>>> > > information for all the jira users from your old project instances. >>>> > > >>>> > > If there are users that are inactive and/or can't be contacted , >>>> let me >>>> > > know that list and I'll prepend all their usernames (ie - >>>> imported-nick) >>>> > > or similar. >>>> > > >>>> > > Once I have all that info I'll start making some test runs. >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > On 9/10/15, 1:29 PM, "Amol Kekre" <[email protected]> wrote: >>>> > > >>>> > > >Chris, >>>> > > >Thanks for helping. We need history, and can make it work for >>>> Gavin if >>>> > > >there is a way out. We can work on which fields to drop etc. >>>> > > > >>>> > > >Thks >>>> > > >Amol >>>> > > > >>>> > > >On Thu, Sep 10, 2015 at 9:47 AM, Chris Nauroth < >>>> > [email protected]> >>>> > > >wrote: >>>> > > > >>>> > > >> Thank you for the responses, everyone. Since many of you value >>>> > > >>retaining >>>> > > >> the history, let's work towards that. >>>> > > >> >>>> > > >> Gavin has asked if we can give him until next week for a more >>>> thorough >>>> > > >> status update on INFRA-10145. Let's wait and see. Maybe he'll >>>> find a >>>> > > >>way >>>> > > >> to streamline the process. >>>> > > >> >>>> > > >> --Chris Nauroth >>>> > > >> >>>> > > >> >>>> > > >> >>>> > > >> >>>> > > >> On 9/10/15, 9:01 AM, "Sasha Parfenov" <[email protected]> >>>> wrote: >>>> > > >> >>>> > > >> >Given the benefits of moving to ASF JIRA, option 3 sounds like >>>> the >>>> > best >>>> > > >> >way >>>> > > >> >to go. >>>> > > >> > >>>> > > >> >On Thursday, September 10, 2015, Milind Barve < >>>> [email protected]> >>>> > > >>wrote: >>>> > > >> > >>>> > > >> >> +1 for 3 from me as well. >>>> > > >> >> On Sep 10, 2015 9:03 PM, "Amol Kekre" <[email protected] >>>> > > >> >><javascript:;>> >>>> > > >> >> wrote: >>>> > > >> >> >>>> > > >> >> > +1 for 3 for me. We have a lot of IP in the current jiras. >>>> > > >> >> > >>>> > > >> >> > Is this doable: Write a script to download key fields of the >>>> > > >>current >>>> > > >> >> > Atlassian jira, and then create these in ASF jira only on >>>> those >>>> > > >>keys. >>>> > > >> >>In >>>> > > >> >> > the process flip the keys like "project" to correct key; and >>>> > users >>>> > > >>to >>>> > > >> >> > "annonymous", drop the watch list. The rest of the keys in >>>> a jira >>>> > > >>can >>>> > > >> >>be >>>> > > >> >> > updated manually as we work off the new jiras. >>>> > > >> >> > >>>> > > >> >> > In my view critical keys are: description, comments, type, >>>> > > >>priority, >>>> > > >> >> > resolution, status >>>> > > >> >> > // We can even add "From >>>> > > >> >>https://malhar.atlassian.net/browse/MLHR-XXXX\n >>>> > > >> >> " >>>> > > >> >> > in the start of description >>>> > > >> >> > >>>> > > >> >> > Thks, >>>> > > >> >> > Amol >>>> > > >> >> > >>>> > > >> >> > >>>> > > >> >> > On Thu, Sep 10, 2015 at 8:21 AM, Pramod Immaneni >>>> > > >> >><[email protected] >>>> > > >> >> <javascript:;>> >>>> > > >> >> > wrote: >>>> > > >> >> > >>>> > > >> >> > > I would like to add +1 for 3. >>>> > > >> >> > > >>>> > > >> >> > > Thanks >>>> > > >> >> > > >>>> > > >> >> > > > On Sep 9, 2015, at 11:02 PM, Chris Nauroth >>>> > > >> >><[email protected] >>>> > > >> >> <javascript:;>> >>>> > > >> >> > > wrote: >>>> > > >> >> > > > >>>> > > >> >> > > > Hello Apex devs, >>>> > > >> >> > > > >>>> > > >> >> > > > I'd like to share some new information about the ASF >>>> JIRA >>>> > > >> >>migration, >>>> > > >> >> > > > tracked in issue INFRA-10145. >>>> > > >> >> > > > >>>> > > >> >> > > > https://issues.apache.org/jira/browse/INFRA-10145 >>>> > > >> >> > > > >>>> > > >> >> > > > First, I'd like to take this opportunity to make sure >>>> the >>>> > whole >>>> > > >> >>Apex >>>> > > >> >> > > > community knows that there are multiple means of >>>> contacting >>>> > the >>>> > > >> >> Apache >>>> > > >> >> > > > infrastructure engineers. This is documented here. >>>> > > >> >> > > > >>>> > > >> >> > > > http://www.apache.org/dev/infra-contact >>>> > > >> >> > > > >>>> > > >> >> > > > My experience has always been that the infrastructure >>>> team is >>>> > > >> >> > responsive, >>>> > > >> >> > > > helpful and friendly. Please feel free to contact them >>>> if >>>> > > >> >>necessary. >>>> > > >> >> > I >>>> > > >> >> > > > typically start by filing an INFRA issue in JIRA, and >>>> then >>>> > > >>follow >>>> > > >> >>up >>>> > > >> >> in >>>> > > >> >> > > > the HipChat channel if there is no response in JIRA >>>> after a >>>> > few >>>> > > >> >>days. >>>> > > >> >> > > > >>>> > > >> >> > > > I checked in at the HipChat channel today about our JIRA >>>> > > >>migration >>>> > > >> >> > > status. >>>> > > >> >> > > > Gavin, who is handling INFRA-10145 for us, was not >>>> available, >>>> > > >>but >>>> > > >> >>the >>>> > > >> >> > > > other infrastructure engineers pointed out a few >>>> challenges. >>>> > > >>The >>>> > > >> >> > version >>>> > > >> >> > > > of JIRA in use hosted at Atlassian is different from the >>>> > > >>version >>>> > > >> >> > > currently >>>> > > >> >> > > > running in Apache. In order to do an import, the >>>> versions >>>> > must >>>> > > >> >>match >>>> > > >> >> > > > exactly, so our import actually would trigger an >>>> upgrade of >>>> > ASF >>>> > > >> >>JIRA. >>>> > > >> >> > > > This would require planned downtime with at least 72 >>>> hours >>>> > > >>notice. >>>> > > >> >> > After >>>> > > >> >> > > > that, there would be some challenges with making sure >>>> > imported >>>> > > >> >>data >>>> > > >> >> > > aligns >>>> > > >> >> > > > with best practices used in ASF JIRA, such as using >>>> roles >>>> > > >>instead >>>> > > >> >>of >>>> > > >> >> > > > groups. Considering all of this, the infrastructure >>>> team's >>>> > > >> >> experience >>>> > > >> >> > is >>>> > > >> >> > > > that imports take a long time, even in the best case. >>>> > > >> >> > > > >>>> > > >> >> > > > The infrastructure team and I discussed a few options >>>> for >>>> > > >>moving >>>> > > >> >> ahead. >>>> > > >> >> > > > >>>> > > >> >> > > > 1. Do not migrate to ASF JIRA. The infrastructure team >>>> noted >>>> > > >>that >>>> > > >> >> > there >>>> > > >> >> > > > is nothing in the incubation process that mandates >>>> moving off >>>> > > >>of >>>> > > >> >>your >>>> > > >> >> > > > Atlassian hosted instance. I had not been aware of >>>> this. >>>> > > >> >> > > > >>>> > > >> >> > > > 2. Move to ASF JIRA, but skip the import, and start >>>> with a >>>> > > >>clean >>>> > > >> >> slate. >>>> > > >> >> > > > >>>> > > >> >> > > > 3. Move to ASF JIRA now, but allow the import activity >>>> to >>>> > > >> >>continue in >>>> > > >> >> > the >>>> > > >> >> > > > background. Once we start using ASF JIRA though, >>>> imported >>>> > > >>issues >>>> > > >> >> would >>>> > > >> >> > > > not be able to land in the same project key. They'd >>>> likely >>>> > > >>have >>>> > > >> >>to >>>> > > >> >> > > remain >>>> > > >> >> > > > under the old project keys used at the Atlassian >>>> instance. >>>> > > >> >> > > > >>>> > > >> >> > > > 4. Keep waiting for the migration with the >>>> understanding that >>>> > > >>it >>>> > > >> >>will >>>> > > >> >> > > take >>>> > > >> >> > > > time to complete. >>>> > > >> >> > > > >>>> > > >> >> > > > I'd like to gauge the Apex community's opinion on how to >>>> > > >>proceed. >>>> > > >> >> My >>>> > > >> >> > own >>>> > > >> >> > > > opinion is that it would be beneficial to move to ASF >>>> JIRA, >>>> > so >>>> > > >>I'd >>>> > > >> >> > prefer >>>> > > >> >> > > > to rule out option 1. One of the benefits of Apex is >>>> its >>>> > > >> >>integration >>>> > > >> >> > > with >>>> > > >> >> > > > numerous other Apache projects, and it can be useful to >>>> share >>>> > > >>the >>>> > > >> >> same >>>> > > >> >> > > > JIRA instance with those other projects. For example, >>>> if you >>>> > > >> >>trace >>>> > > >> >> the >>>> > > >> >> > > > root cause of an Apex issue into HDFS, and you want to >>>> > contact >>>> > > >>an >>>> > > >> >> HDFS >>>> > > >> >> > > > engineer, you can ask me for feedback by entering >>>> @cnauroth >>>> > on >>>> > > >>a >>>> > > >> >> > comment. >>>> > > >> >> > > > If you remain in the Atlassian instance, it's not >>>> guaranteed >>>> > > >>that >>>> > > >> >> > > > contributors on other Apache projects will have an >>>> account >>>> > > >>there. >>>> > > >> >> If >>>> > > >> >> > the >>>> > > >> >> > > > issue is confirmed as an HDFS bug, you can then link >>>> your >>>> > Apex >>>> > > >> >>issue >>>> > > >> >> to >>>> > > >> >> > > > the corresponding HDFS issue for easy navigation. I >>>> don't >>>> > > >>believe >>>> > > >> >> this >>>> > > >> >> > > > would work as cleanly in the Atlassian instance. >>>> > > >> >> > > > >>>> > > >> >> > > > My preference is option 2 for simplicity. However, >>>> this has >>>> > > >>the >>>> > > >> >>side >>>> > > >> >> > > > effect of discarding past history. Does the Apex >>>> community >>>> > > >> >>consider >>>> > > >> >> > the >>>> > > >> >> > > > past history to be important? Is it important enough to >>>> > > >>preserve >>>> > > >> >>the >>>> > > >> >> > > past >>>> > > >> >> > > > history that you're willing to wait longer for a >>>> migration? >>>> > > >> >> > > > >>>> > > >> >> > > > Please let me know your thoughts. >>>> > > >> >> > > > >>>> > > >> >> > > > --Chris Nauroth >>>> > > >> >> > > > >>>> > > >> >> > > >>>> > > >> >> > >>>> > > >> >> >>>> > > >> >>>> > > >> >>>> > > >>>> > > >>>> > >>>> >>> >>> >>> >> >
