@Andrew, Thanks, we probably should only do manual migration, so that the text in Jira is not messed up. And I think we should only import issues that are still open.
On Sat, Apr 2, 2016 at 2:53 AM, Andrew Purtell <[email protected]> wrote: > We used the GitHub to JIRA import option when starting up the Phoenix > podling. I didn't like the outcome. As an example please see > https://issues.apache.org/jira/browse/PHOENIX-672 > > On Fri, Apr 1, 2016 at 12:11 AM, Karol Brejna <[email protected]> > wrote: > > > ’ve extracted open issues to excel file. Maybe we could put them on > google > > docs (sheet) and do „marking” of which should „survive” the migration > there > > (collaboratively, maybe each reporter could decide on his own request, > > whatever). > > > > I also see “import issues” in apache jira. If we are brave enough we > could > > try this option (needs issues stored in csv – no problem here). > > > > If not we could cherry pick issues and insert them manually. > > > > Karol > > > > śr., 30.03.2016 o 05:37 użytkownik Weihua Jiang <[email protected]> > > napisał: > > > > > Do we want a 1:1 mapping or cherry picking? > > > > > > Thanks > > > Weihua > > > > > > > > > > > > 在 16/3/30 上午11:05，“Sean Zhong”<[email protected]> 写入: > > > > > > >If everyone is OK, I'd like to migrate the Github issues to Apache > Jira. > > > It > > > >means we need to copy the issue list from Github and re-create them in > > > Jira. > > > > > > > >The Github issue list: https://github.com/gearpump/gearpump/issues > > > >The Apache Jira home: https://issues.apache.org/jira/browse/GEARPUMP > > > > > > > >Thanks > > > > > > > >Sean > > > > > > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
