Yes. If agreed, I'll create a jira and amend the commit. On Wed, Apr 6, 2016 at 11:14 AM Kam Kasravi <[email protected]> wrote:
> +1 although I thought this was already in a PR? > > On Tuesday, April 5, 2016 6:23 PM, Manu Zhang <[email protected]> > wrote: > > > Hi all, > > I'd like to include https://github.com/gearpump/gearpump/issues/2013 > (Refactor > DataSource API). > What do you think ? > > On Wed, Apr 6, 2016 at 8:50 AM Kam Kasravi <[email protected]> > wrote: > > > Sonatype project for gearpump ticket has been createdhttps:// > > issues.sonatype.org/browse/OSSRH-21642 > > > > > > > > > > On Tuesday, April 5, 2016 9:24 AM, Kam Kasravi > > <[email protected]> wrote: > > > > > > These are the issues that are excluded from migration > > > https://github.com/gearpump/gearpump/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone > > > > > > > > > > On Monday, April 4, 2016 11:41 PM, Sean Zhong <[email protected]> > > wrote: > > > > > > Hi all, > > > > I have created a milestone named "Apache Migration" at > > > > > https://github.com/gearpump/gearpump/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Apache+Migration%22 > > > > Would you please check whether this list contains all issues that we want > > to migrate? And please modify them if you think the list is missing some > > items. > > > > Reminder: All issues that are not in this list will be closed in Github > > after the migration. > > > > > > Sean > > > > On Tue, Apr 5, 2016 at 2:38 PM, Sean Zhong <[email protected]> wrote: > > > > > @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) > > >> > > > > > > > > > > > > > > > >
