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 <c...@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. <abezzu...@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.