You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Alex B." <bz...@apache.org> on 2015/01/11 13:17:18 UTC
Project GH issue-tracker transition to ASF JIRA
Hey guys,
we just got JIRA up and working (thanks to awesome INFRA!) and I think we
want subj now.
What I'v learned from Flink
<https://issues.apache.org/jira/browse/INFRA-7871> example so far is that
INFRA team is not going to do that for us. Assuming that, I can will take
care of this transition in a next couple of days.
My current plan is to use some existing tools
<https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
issues using it's API and then push them to JIRA though it's API.
Tech Details:
To keep issue numbers same, it's important to start with empty JIRA project
as we have it how.
All comments from GH issues will be created under its own userid
"github-import" with orig. author name added to the comment.
As we have only 57 issues (36 open\21 closed) - be prepared for some
notification emails. In case that's not appropriate I could try bothering
INFRA with asking to turn notifications off, so let me know if that's
desired.
Please, let me know what you think.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by "Alex B." <bz...@apache.org>.
Thanks a lot, Robert,
for a great tool which for sure deserves an it's own repo, advices and your
interest in Zeppelin.
We definitely are looking forward Flink integration, so please also do not
hesitate to ask any questions, help, etc!
Will keep this thread posted on migration process.
On Sun, Jan 11, 2015 at 9:37 PM, Robert Metzger <rm...@apache.org> wrote:
> Hi guys,
>
> I'm the author of the mentioned tool and I also did the import of the JIRAs
> for Flink. Let me know if you encounter any issues.
> The tool will create 278 (or your current id) JIRA issues, because its
> importing the closed ones as well. Github is treating pull requests and
> issues the same way, so it will also create JIRAs for pull requests (which
> is fine for you as well I guess).
> I also asked infra to turn off the jira notifications for the import. I can
> recommend asking them on https://apache.hipchat.com/chat for stuff like
> that.
>
> You are now the third incubator podling to use the tool ;) .. I think I'm
> putting the tool into its own GitHub repository.
>
> On a side note: I tried out Zeppelin yesterday .. Its working really well!
> The maven build worked like charm, the tutorial also worked.
> I also started looking into the code for integrating it with Flink. I think
> I can create a first prototype quite soon.
>
> Best,
> Robert
>
>
>
>
> On Sun, Jan 11, 2015 at 1:17 PM, Alex B. <bz...@apache.org> wrote:
>
> > Hey guys,
> >
> > we just got JIRA up and working (thanks to awesome INFRA!) and I think we
> > want subj now.
> >
> > What I'v learned from Flink
> > <https://issues.apache.org/jira/browse/INFRA-7871> example so far is
> that
> > INFRA team is not going to do that for us. Assuming that, I can will take
> > care of this transition in a next couple of days.
> >
> > My current plan is to use some existing tools
> > <https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
> > issues using it's API and then push them to JIRA though it's API.
> >
> > Tech Details:
> > To keep issue numbers same, it's important to start with empty JIRA
> project
> > as we have it how.
> >
> > All comments from GH issues will be created under its own userid
> > "github-import" with orig. author name added to the comment.
> >
> > As we have only 57 issues (36 open\21 closed) - be prepared for some
> > notification emails. In case that's not appropriate I could try bothering
> > INFRA with asking to turn notifications off, so let me know if that's
> > desired.
> >
> > Please, let me know what you think.
> >
>
Re: Project GH issue-tracker transition to ASF JIRA
Posted by moon soo Lee <mo...@apache.org>.
If we can use some kind of system user, that would be better. But i'm
totally fine with using one of PPMC account.
Thanks,
moon
On Wed, Mar 25, 2015 at 10:48 AM Alex B. <ab...@nflabs.com> wrote:
> 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. <bz...@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 <roman@shaposhnik.org
> >
> > wrote:
> >
> > > On Mon, Jan 12, 2015 at 12:33 AM, Alex B. <bz...@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.
>
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Alexander Bezzubov <bz...@apache.org>.
Adding David back to the discussion.
David, we would appreciate your advice, couple of questions are in prev.
message below.
Thank you!
---------- Forwarded message ----------
From: Alex B. <ab...@nflabs.com>
Date: Fri, Mar 27, 2015 at 3:39 PM
Subject: Re: Project GH issue-tracker transition to ASF JIRA
To: "dev@zeppelin.incubator.apache.org" <de...@zeppelin.incubator.apache.org>
Cc: Roman Shaposhnik <ro...@shaposhnik.org>, andrew bayer <abayer@apache.org
>
Hi David,
thank you for the suggestion, I looked it up here
https://confluence.atlassian.com/display/JIRA/Importing+Data+from+Github
Could you please share some details on your experience with this tool? What
kind of coordination does it require?
It mentioned "Log in to JIRA as a user with the JIRA Administrators global
permission." and after couple of attempts it seems to me that project admin
rights in JIRA is not enough to make it work.
Or am I missing something?
If it requires an INFRA issue - could you please point to an examples?
Thanks in advance.
On Fri, Mar 27, 2015 at 6:51 AM, David Nalley <da...@gnsa.us> wrote:
> Jira has a GH migration tool built in - and we've used that a number
> of times recently. It requires some coordination, and isn't perfect,
> but it works.
>
> --David
>
> On Wed, Mar 25, 2015 at 6:44 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
> > +Andrew and David (who may know how this is being done recently)
> >
> > On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
> >> 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.
> >
> > A few years ago I was using hadoopqa user account to transition
> > a project from GH issues to JIRA.
> >
> > Andrew, David, what is considered best practice these days?
> >
> >> 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.
> >
> > Personally -- I don't really care that much as long as these issues all
> go
> > to a dedicated email address that I can easily filter out.
> >
> > Thanks,
> > Roman.
>
--
--
Kind regards,
Alexander.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by "Alex B." <ab...@nflabs.com>.
Hi David,
thank you for the suggestion, I looked it up here
https://confluence.atlassian.com/display/JIRA/Importing+Data+from+Github
Could you please share some details on your experience with this tool? What
kind of coordination does it require?
It mentioned "Log in to JIRA as a user with the JIRA Administrators global
permission." and after couple of attempts it seems to me that project admin
rights in JIRA is not enough to make it work.
Or am I missing something?
If it requires an INFRA issue - could you please point to an examples?
Thanks in advance.
On Fri, Mar 27, 2015 at 6:51 AM, David Nalley <da...@gnsa.us> wrote:
> Jira has a GH migration tool built in - and we've used that a number
> of times recently. It requires some coordination, and isn't perfect,
> but it works.
>
> --David
>
> On Wed, Mar 25, 2015 at 6:44 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
> > +Andrew and David (who may know how this is being done recently)
> >
> > On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
> >> 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.
> >
> > A few years ago I was using hadoopqa user account to transition
> > a project from GH issues to JIRA.
> >
> > Andrew, David, what is considered best practice these days?
> >
> >> 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.
> >
> > Personally -- I don't really care that much as long as these issues all
> go
> > to a dedicated email address that I can easily filter out.
> >
> > Thanks,
> > Roman.
>
--
--
Kind regards,
Alexander.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by David Nalley <da...@gnsa.us>.
Jira has a GH migration tool built in - and we've used that a number
of times recently. It requires some coordination, and isn't perfect,
but it works.
--David
On Wed, Mar 25, 2015 at 6:44 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> +Andrew and David (who may know how this is being done recently)
>
> On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
>> 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.
>
> A few years ago I was using hadoopqa user account to transition
> a project from GH issues to JIRA.
>
> Andrew, David, what is considered best practice these days?
>
>> 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.
>
> Personally -- I don't really care that much as long as these issues all go
> to a dedicated email address that I can easily filter out.
>
> Thanks,
> Roman.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Mar 25, 2015 at 04:16PM, Henry Saputra wrote:
> Yep, but in this case, it will still create hundreds of emails to dev@
> because it is considered as create event.
Then perhaps for the time being _all_ notifications could be send to issue@
and later on dup. for the CREATE event can be added for dev@ ??
>
> - Henry
>
> On Wed, Mar 25, 2015 at 4:10 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > On Wed, Mar 25, 2015 at 03:44PM, Roman Shaposhnik wrote:
> >> +Andrew and David (who may know how this is being done recently)
> >>
> >> On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
> >> > 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.
> >>
> >> A few years ago I was using hadoopqa user account to transition
> >> a project from GH issues to JIRA.
> >
> > I just did something like that for Ignite. You can create a brand-new account
> > in JIRA and use it to report/comment on the project's issues. It doesn't have
> > to be a user in the Jenkins' setup - can be anything you want. In case of
> > Ignite it is ignite-ci.'
> >
> >>
> >> Andrew, David, what is considered best practice these days?
> >>
> >> > 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.
> >
> > For Ignite (kudos to Henry Saputra) and most recently for Bigtop we have
> > created a separate issues@ lists to send in all notifications except of
> > CREATE. See https://issues.apache.org/jira/browse/INFRA-9330 as an example.
> >
> >>
> >> Personally -- I don't really care that much as long as these issues all go
> >> to a dedicated email address that I can easily filter out.
> >>
> >> Thanks,
> >> Roman.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Henry Saputra <he...@gmail.com>.
Yep, but in this case, it will still create hundreds of emails to dev@
because it is considered as create event.
- Henry
On Wed, Mar 25, 2015 at 4:10 PM, Konstantin Boudnik <co...@apache.org> wrote:
> On Wed, Mar 25, 2015 at 03:44PM, Roman Shaposhnik wrote:
>> +Andrew and David (who may know how this is being done recently)
>>
>> On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
>> > 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.
>>
>> A few years ago I was using hadoopqa user account to transition
>> a project from GH issues to JIRA.
>
> I just did something like that for Ignite. You can create a brand-new account
> in JIRA and use it to report/comment on the project's issues. It doesn't have
> to be a user in the Jenkins' setup - can be anything you want. In case of
> Ignite it is ignite-ci.'
>
>>
>> Andrew, David, what is considered best practice these days?
>>
>> > 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.
>
> For Ignite (kudos to Henry Saputra) and most recently for Bigtop we have
> created a separate issues@ lists to send in all notifications except of
> CREATE. See https://issues.apache.org/jira/browse/INFRA-9330 as an example.
>
>>
>> Personally -- I don't really care that much as long as these issues all go
>> to a dedicated email address that I can easily filter out.
>>
>> Thanks,
>> Roman.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Mar 25, 2015 at 03:44PM, Roman Shaposhnik wrote:
> +Andrew and David (who may know how this is being done recently)
>
> On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
> > 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.
>
> A few years ago I was using hadoopqa user account to transition
> a project from GH issues to JIRA.
I just did something like that for Ignite. You can create a brand-new account
in JIRA and use it to report/comment on the project's issues. It doesn't have
to be a user in the Jenkins' setup - can be anything you want. In case of
Ignite it is ignite-ci.'
>
> Andrew, David, what is considered best practice these days?
>
> > 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.
For Ignite (kudos to Henry Saputra) and most recently for Bigtop we have
created a separate issues@ lists to send in all notifications except of
CREATE. See https://issues.apache.org/jira/browse/INFRA-9330 as an example.
>
> Personally -- I don't really care that much as long as these issues all go
> to a dedicated email address that I can easily filter out.
>
> Thanks,
> Roman.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
+Andrew and David (who may know how this is being done recently)
On Tue, Mar 24, 2015 at 6:47 PM, Alex B. <ab...@nflabs.com> wrote:
> 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.
A few years ago I was using hadoopqa user account to transition
a project from GH issues to JIRA.
Andrew, David, what is considered best practice these days?
> 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.
Personally -- I don't really care that much as long as these issues all go
to a dedicated email address that I can easily filter out.
Thanks,
Roman.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by "Alex B." <ab...@nflabs.com>.
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. <bz...@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. <bz...@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.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by "Alex B." <bz...@apache.org>.
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. <bz...@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.
>
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Jan 12, 2015 at 12:33 AM, Alex B. <bz...@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.
Re: Project GH issue-tracker transition to ASF JIRA
Posted by "Alex B." <bz...@apache.org>.
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.
Otherwise I can only import them all from my user account which does not
make much sense.
Is going to be ~270 emails :)
Asked INFRA to disable notifications temporary but got rejected as "mailing
lists are archives of the project for the Foundation", which sounds
reasonable to me.
On Sun, Jan 11, 2015 at 10:00 PM, moon soo Lee <mo...@apache.org> wrote:
> Hi,
>
> Alexander, I think it's cool plan! (by the way, to me 57 emails are totally
> okay)
>
> Robert, it's truly great to hear about integration with Flink!
>
> Best,
> moon
>
>
>
> On Sun, Jan 11, 2015 at 9:37 PM, Robert Metzger <rm...@apache.org>
> wrote:
>
> > Hi guys,
> >
> > I'm the author of the mentioned tool and I also did the import of the
> JIRAs
> > for Flink. Let me know if you encounter any issues.
> > The tool will create 278 (or your current id) JIRA issues, because its
> > importing the closed ones as well. Github is treating pull requests and
> > issues the same way, so it will also create JIRAs for pull requests
> (which
> > is fine for you as well I guess).
> > I also asked infra to turn off the jira notifications for the import. I
> can
> > recommend asking them on https://apache.hipchat.com/chat for stuff like
> > that.
> >
> > You are now the third incubator podling to use the tool ;) .. I think I'm
> > putting the tool into its own GitHub repository.
> >
> > On a side note: I tried out Zeppelin yesterday .. Its working really
> well!
> > The maven build worked like charm, the tutorial also worked.
> > I also started looking into the code for integrating it with Flink. I
> think
> > I can create a first prototype quite soon.
> >
> > Best,
> > Robert
> >
> >
> >
> >
> > On Sun, Jan 11, 2015 at 1:17 PM, Alex B. <bz...@apache.org> wrote:
> >
> > > Hey guys,
> > >
> > > we just got JIRA up and working (thanks to awesome INFRA!) and I think
> we
> > > want subj now.
> > >
> > > What I'v learned from Flink
> > > <https://issues.apache.org/jira/browse/INFRA-7871> example so far is
> > that
> > > INFRA team is not going to do that for us. Assuming that, I can will
> take
> > > care of this transition in a next couple of days.
> > >
> > > My current plan is to use some existing tools
> > > <https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
> > > issues using it's API and then push them to JIRA though it's API.
> > >
> > > Tech Details:
> > > To keep issue numbers same, it's important to start with empty JIRA
> > project
> > > as we have it how.
> > >
> > > All comments from GH issues will be created under its own userid
> > > "github-import" with orig. author name added to the comment.
> > >
> > > As we have only 57 issues (36 open\21 closed) - be prepared for some
> > > notification emails. In case that's not appropriate I could try
> bothering
> > > INFRA with asking to turn notifications off, so let me know if that's
> > > desired.
> > >
> > > Please, let me know what you think.
> > >
> >
>
Re: Project GH issue-tracker transition to ASF JIRA
Posted by moon soo Lee <mo...@apache.org>.
Hi,
Alexander, I think it's cool plan! (by the way, to me 57 emails are totally
okay)
Robert, it's truly great to hear about integration with Flink!
Best,
moon
On Sun, Jan 11, 2015 at 9:37 PM, Robert Metzger <rm...@apache.org> wrote:
> Hi guys,
>
> I'm the author of the mentioned tool and I also did the import of the JIRAs
> for Flink. Let me know if you encounter any issues.
> The tool will create 278 (or your current id) JIRA issues, because its
> importing the closed ones as well. Github is treating pull requests and
> issues the same way, so it will also create JIRAs for pull requests (which
> is fine for you as well I guess).
> I also asked infra to turn off the jira notifications for the import. I can
> recommend asking them on https://apache.hipchat.com/chat for stuff like
> that.
>
> You are now the third incubator podling to use the tool ;) .. I think I'm
> putting the tool into its own GitHub repository.
>
> On a side note: I tried out Zeppelin yesterday .. Its working really well!
> The maven build worked like charm, the tutorial also worked.
> I also started looking into the code for integrating it with Flink. I think
> I can create a first prototype quite soon.
>
> Best,
> Robert
>
>
>
>
> On Sun, Jan 11, 2015 at 1:17 PM, Alex B. <bz...@apache.org> wrote:
>
> > Hey guys,
> >
> > we just got JIRA up and working (thanks to awesome INFRA!) and I think we
> > want subj now.
> >
> > What I'v learned from Flink
> > <https://issues.apache.org/jira/browse/INFRA-7871> example so far is
> that
> > INFRA team is not going to do that for us. Assuming that, I can will take
> > care of this transition in a next couple of days.
> >
> > My current plan is to use some existing tools
> > <https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
> > issues using it's API and then push them to JIRA though it's API.
> >
> > Tech Details:
> > To keep issue numbers same, it's important to start with empty JIRA
> project
> > as we have it how.
> >
> > All comments from GH issues will be created under its own userid
> > "github-import" with orig. author name added to the comment.
> >
> > As we have only 57 issues (36 open\21 closed) - be prepared for some
> > notification emails. In case that's not appropriate I could try bothering
> > INFRA with asking to turn notifications off, so let me know if that's
> > desired.
> >
> > Please, let me know what you think.
> >
>
Re: Project GH issue-tracker transition to ASF JIRA
Posted by Robert Metzger <rm...@apache.org>.
Hi guys,
I'm the author of the mentioned tool and I also did the import of the JIRAs
for Flink. Let me know if you encounter any issues.
The tool will create 278 (or your current id) JIRA issues, because its
importing the closed ones as well. Github is treating pull requests and
issues the same way, so it will also create JIRAs for pull requests (which
is fine for you as well I guess).
I also asked infra to turn off the jira notifications for the import. I can
recommend asking them on https://apache.hipchat.com/chat for stuff like
that.
You are now the third incubator podling to use the tool ;) .. I think I'm
putting the tool into its own GitHub repository.
On a side note: I tried out Zeppelin yesterday .. Its working really well!
The maven build worked like charm, the tutorial also worked.
I also started looking into the code for integrating it with Flink. I think
I can create a first prototype quite soon.
Best,
Robert
On Sun, Jan 11, 2015 at 1:17 PM, Alex B. <bz...@apache.org> wrote:
> Hey guys,
>
> we just got JIRA up and working (thanks to awesome INFRA!) and I think we
> want subj now.
>
> What I'v learned from Flink
> <https://issues.apache.org/jira/browse/INFRA-7871> example so far is that
> INFRA team is not going to do that for us. Assuming that, I can will take
> care of this transition in a next couple of days.
>
> My current plan is to use some existing tools
> <https://github.com/rmetzger/scratch/tree/github2jira> to dump Github
> issues using it's API and then push them to JIRA though it's API.
>
> Tech Details:
> To keep issue numbers same, it's important to start with empty JIRA project
> as we have it how.
>
> All comments from GH issues will be created under its own userid
> "github-import" with orig. author name added to the comment.
>
> As we have only 57 issues (36 open\21 closed) - be prepared for some
> notification emails. In case that's not appropriate I could try bothering
> INFRA with asking to turn notifications off, so let me know if that's
> desired.
>
> Please, let me know what you think.
>