Updates on Zeppelin GH->ASF JIRA issue tracker migration: we are ready to do it now!
Current plan is to use Robert's https://github.com/rmetzger/scratch/tree/github2jira The only question so far is the ASF JIRA credentials for a user which will be a "Reporter" of all migrated issues. We could either use one of the PPMCs or some kind of "system" level user. Another seems to be controversial matter is the notification on issue creation (~500 emails will be created). I have contacted INFRA on HipChat before, to ask if that's possible to mute notification and was told that it's not preferable way and we should keep notifications as those emails supposed to be part of the mailing list archive under ASF. Any advice from mentors\more experience folks on the matter is warmly welcome! In case there's non, I assume lazy consensus and going to proceed with the plan from above, with one of the PPMCs JIRA accounts if nobody objects in the next 24 hours. Thanks in advance, Alex. On Wed, Jan 21, 2015 at 10:26 AM, Alex B. <b...@apache.org> wrote: > Current plan on Subj is to do it as a last step of whole migration process: > right after source code is moved to ASF Git and Github mirror is created. > > FYI: sign-up is disabled now on old project JIRA > https://zeppelin-project.atlassian.net and as soon as issues are migrated > I > think we will add a notice like > https://spark-project.atlassian.net/browse/SPARK and send email > notification to all registered users there > > On Tue, Jan 13, 2015 at 12:42 AM, Roman Shaposhnik <ro...@shaposhnik.org> > wrote: > > > On Mon, Jan 12, 2015 at 12:33 AM, Alex B. <b...@apache.org> wrote: > > > Can somebody who have access please help me to add a new JIRA user i.e > > > "github-import"? > > > Or advice on the other ways to make it happen. > > > > There's a hadoopqa account that virtually every single > > project in Hadoop ecosystem used to do that sort of > > thing. I can communicate creds off-list. > > > > > Is going to be ~270 emails :) > > > > Not neccesserily a lot of times JIRA has an 'silent' > > option for bulk updates. I know for a fact that's how > > it works via UI, but pretty sure it should be REST > > option as well. > > > > Thanks, > > Roman. > > > -- -- Kind regards, Alexander.
