You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by Sean Zhong <cl...@gmail.com> on 2016/03/30 05:05:54 UTC
Discussion: Migrate Github issues to Apache JIra
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
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Manu Zhang <ow...@gmail.com>.
How about we firstly give a time frame to allow the issue authors to
migrate our own issues respectively ?
On Fri, Apr 1, 2016 at 3:11 PM Karol Brejna <ka...@gmail.com> 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 <wh...@outlook.com>
> napisał:
>
> > Do we want a 1:1 mapping or cherry picking?
> >
> > Thanks
> > Weihua
> >
> >
> >
> > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> >
> > >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
> >
> >
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Manu Zhang <ow...@gmail.com>.
Hi all,
We've migrated existing GitHub issues
<https://github.com/gearpump/gearpump/issues> to
https://issues.apache.org/jira/browse/GEARPUMP and closed those no longer
invalid.
Please check it out and here is more information.
1. You may follow the link from GitHub issue to Gearpump Jira issue.
2. Sorry if there are valid GitHub issues we closed accidentally, and
please open new Jira issues for it.
3. If a Jira issue is invalid or already solved, please close or resolve
it.
3. We try to maintain as much history and context as possible and also link
back to GitHub issue for your reference. Feel free to add and comment if
you think anything is missing.
4. Some Jira issues don't have component labels yet and some may be labeled
incorrectly, please help to attach proper labels.
5. Please open new issues at https://issues.apache.org/jira/browse/GEARPUMP.
Thanks everyone for your contributions.
Regards,
Manu
On Wed, Apr 6, 2016 at 11:24 AM Manu Zhang <ow...@gmail.com> wrote:
> Yes. If agreed, I'll create a jira and amend the commit.
>
> On Wed, Apr 6, 2016 at 11:14 AM Kam Kasravi <ka...@yahoo.com.invalid>
> wrote:
>
>> +1 although I thought this was already in a PR?
>>
>> On Tuesday, April 5, 2016 6:23 PM, Manu Zhang <
>> owenzhang1990@gmail.com> 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 <ka...@yahoo.com.invalid>
>> 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
>> > <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com>
>> > 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 <cl...@gmail.com> 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 <ap...@apache.org>
>> > > 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 <
>> karol.brejna@gmail.com>
>> > >> 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 <
>> whjiang@outlook.com>
>> > >> > napisał:
>> > >> >
>> > >> > > Do we want a 1:1 mapping or cherry picking?
>> > >> > >
>> > >> > > Thanks
>> > >> > > Weihua
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >> > >
>> > >> > > >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)
>> > >>
>> > >
>> > >
>> >
>> >
>> >
>> >
>>
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Manu Zhang <ow...@gmail.com>.
Hi all,
We've migrated existing GitHub issues
<https://github.com/gearpump/gearpump/issues> to
https://issues.apache.org/jira/browse/GEARPUMP and closed those no longer
invalid.
Please check it out and here is more information.
1. You may follow the link from GitHub issue to Gearpump Jira issue.
2. Sorry if there are valid GitHub issues we closed accidentally, and
please open new Jira issues for it.
3. If a Jira issue is invalid or already solved, please close or resolve
it.
3. We try to maintain as much history and context as possible and also link
back to GitHub issue for your reference. Feel free to add and comment if
you think anything is missing.
4. Some Jira issues don't have component labels yet and some may be labeled
incorrectly, please help to attach proper labels.
5. Please open new issues at https://issues.apache.org/jira/browse/GEARPUMP.
Thanks everyone for your contributions.
Regards,
Manu
On Wed, Apr 6, 2016 at 11:24 AM Manu Zhang <ow...@gmail.com> wrote:
> Yes. If agreed, I'll create a jira and amend the commit.
>
> On Wed, Apr 6, 2016 at 11:14 AM Kam Kasravi <ka...@yahoo.com.invalid>
> wrote:
>
>> +1 although I thought this was already in a PR?
>>
>> On Tuesday, April 5, 2016 6:23 PM, Manu Zhang <
>> owenzhang1990@gmail.com> 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 <ka...@yahoo.com.invalid>
>> 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
>> > <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com>
>> > 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 <cl...@gmail.com> 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 <ap...@apache.org>
>> > > 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 <
>> karol.brejna@gmail.com>
>> > >> 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 <
>> whjiang@outlook.com>
>> > >> > napisał:
>> > >> >
>> > >> > > Do we want a 1:1 mapping or cherry picking?
>> > >> > >
>> > >> > > Thanks
>> > >> > > Weihua
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >> > >
>> > >> > > >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)
>> > >>
>> > >
>> > >
>> >
>> >
>> >
>> >
>>
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Manu Zhang <ow...@gmail.com>.
Yes. If agreed, I'll create a jira and amend the commit.
On Wed, Apr 6, 2016 at 11:14 AM Kam Kasravi <ka...@yahoo.com.invalid>
wrote:
> +1 although I thought this was already in a PR?
>
> On Tuesday, April 5, 2016 6:23 PM, Manu Zhang <ow...@gmail.com>
> 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 <ka...@yahoo.com.invalid>
> 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
> > <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com>
> > 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 <cl...@gmail.com> 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 <ap...@apache.org>
> > > 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 <karol.brejna@gmail.com
> >
> > >> 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 <
> whjiang@outlook.com>
> > >> > napisał:
> > >> >
> > >> > > Do we want a 1:1 mapping or cherry picking?
> > >> > >
> > >> > > Thanks
> > >> > > Weihua
> > >> > >
> > >> > >
> > >> > >
> > >> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> > >> > >
> > >> > > >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)
> > >>
> > >
> > >
> >
> >
> >
> >
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Kam Kasravi <ka...@yahoo.com.INVALID>.
+1 although I thought this was already in a PR?
On Tuesday, April 5, 2016 6:23 PM, Manu Zhang <ow...@gmail.com> 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 <ka...@yahoo.com.invalid>
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
> <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com>
> 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 <cl...@gmail.com> 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 <ap...@apache.org>
> > 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 <ka...@gmail.com>
> >> 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 <wh...@outlook.com>
> >> > napisał:
> >> >
> >> > > Do we want a 1:1 mapping or cherry picking?
> >> > >
> >> > > Thanks
> >> > > Weihua
> >> > >
> >> > >
> >> > >
> >> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> >> > >
> >> > > >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)
> >>
> >
> >
>
>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Manu Zhang <ow...@gmail.com>.
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 <ka...@yahoo.com.invalid>
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
> <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com>
> 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 <cl...@gmail.com> 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 <ap...@apache.org>
> > 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 <ka...@gmail.com>
> >> 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 <wh...@outlook.com>
> >> > napisał:
> >> >
> >> > > Do we want a 1:1 mapping or cherry picking?
> >> > >
> >> > > Thanks
> >> > > Weihua
> >> > >
> >> > >
> >> > >
> >> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> >> > >
> >> > > >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)
> >>
> >
> >
>
>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Kam Kasravi <ka...@yahoo.com.INVALID>.
Sonatype project for gearpump ticket has been createdhttps://issues.sonatype.org/browse/OSSRH-21642
On Tuesday, April 5, 2016 9:24 AM, Kam Kasravi <ka...@yahoo.com.INVALID> 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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <ap...@apache.org>
> 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 <ka...@gmail.com>
>> 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 <wh...@outlook.com>
>> > napisał:
>> >
>> > > Do we want a 1:1 mapping or cherry picking?
>> > >
>> > > Thanks
>> > > Weihua
>> > >
>> > >
>> > >
>> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >
>> > > >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)
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Kam Kasravi <ka...@yahoo.com.INVALID>.
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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <ap...@apache.org>
> 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 <ka...@gmail.com>
>> 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 <wh...@outlook.com>
>> > napisał:
>> >
>> > > Do we want a 1:1 mapping or cherry picking?
>> > >
>> > > Thanks
>> > > Weihua
>> > >
>> > >
>> > >
>> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >
>> > > >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)
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Kam Kasravi <ka...@yahoo.com.INVALID>.
As we move issues over to JIRA should we close the github issues (after adding the JIRA cross reference)?
On Monday, April 4, 2016 11:41 PM, Sean Zhong <cl...@gmail.com> 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 <cl...@gmail.com> 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 <ap...@apache.org>
> 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 <ka...@gmail.com>
>> 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 <wh...@outlook.com>
>> > napisał:
>> >
>> > > Do we want a 1:1 mapping or cherry picking?
>> > >
>> > > Thanks
>> > > Weihua
>> > >
>> > >
>> > >
>> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >
>> > > >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)
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Sean Zhong <cl...@gmail.com>.
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 <cl...@gmail.com> 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 <ap...@apache.org>
> 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 <ka...@gmail.com>
>> 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 <wh...@outlook.com>
>> > napisał:
>> >
>> > > Do we want a 1:1 mapping or cherry picking?
>> > >
>> > > Thanks
>> > > Weihua
>> > >
>> > >
>> > >
>> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>> > >
>> > > >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)
>>
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Sean Zhong <cl...@gmail.com>.
@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 <ap...@apache.org> 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 <ka...@gmail.com>
> 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 <wh...@outlook.com>
> > napisał:
> >
> > > Do we want a 1:1 mapping or cherry picking?
> > >
> > > Thanks
> > > Weihua
> > >
> > >
> > >
> > > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> > >
> > > >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)
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Andrew Purtell <ap...@apache.org>.
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 <ka...@gmail.com>
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 <wh...@outlook.com>
> napisał:
>
> > Do we want a 1:1 mapping or cherry picking?
> >
> > Thanks
> > Weihua
> >
> >
> >
> > 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
> >
> > >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)
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Karol Brejna <ka...@gmail.com>.
’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 <wh...@outlook.com>
napisał:
> Do we want a 1:1 mapping or cherry picking?
>
> Thanks
> Weihua
>
>
>
> 在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>
> >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
>
>
Re: Discussion: Migrate Github issues to Apache JIra
Posted by Weihua Jiang <wh...@outlook.com>.
Do we want a 1:1 mapping or cherry picking?
Thanks
Weihua
在 16/3/30 上午11:05，“Sean Zhong”<cl...@gmail.com> 写入:
>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