in my experience typically such changes require jira admin rights, enter an INFRA jira.
On Tue, Sep 13, 2011 at 9:05 AM, Andrew Bayer <[email protected]> wrote: > INFRA JIRA is probably the way to go. > > A. > > On Tue, Sep 13, 2011 at 8:47 AM, Roman Shaposhnik <[email protected]> wrote: > >> On Sun, Sep 11, 2011 at 2:21 PM, Konstantin Boudnik <[email protected]> >> wrote: >> > Right. This is what I was kinda referring as a separate list for >> notification >> > in my OP (Hadoop keep separate *-issues@ list for every component). >> However, >> > the mixed approached might be even better as it allows to avoid any >> update >> > traffic unless a person is specifically watching an issue. >> > >> > To summarize (under assumption that *-issues@ list is being created) >> > - JIRA create notifications are to go to bigtop-dev@ and >> > bigtop-issues@lists >> > - following updates to go only to bigtop-issues@ list >> >> I think we all agree on the above. >> >> At this point, do we need to chant to get attention of one of the >> Apache arhats? >> Or should we just file an INFRA JIRA? >> >> Thanks, >> Roman. >> >
