I just gave you committer permissions on JIRA, try now? On Mon, May 16, 2016 at 12:03 AM, Zheng, Kai <kai.zh...@intel.com> wrote:
> I just ran into the bad situation that I committed HDFS-8449 but can't > resolve the issue due to lacking the required permission to me. Am not sure > if it's caused by my setup or environment change (temporally working in a > new time zone). Would anyone help resolve the issue for me to avoid bad > state? Thanks! > > -----Original Message----- > From: Zheng, Kai [mailto:kai.zh...@intel.com] > Sent: Sunday, May 15, 2016 3:20 PM > To: Allen Wittenauer <allenwittena...@yahoo.com.INVALID> > Cc: common-dev@hadoop.apache.org > Subject: RE: Different JIRA permissions for HADOOP and HDFS > > Thanks Allen for illustrating this in details. I understand. The left > question is, is it intended only JIRA owner (not sure about admin users) > can do the operations like updating a patch? > > Regards, > Kai > > -----Original Message----- > From: Allen Wittenauer [mailto:allenwittena...@yahoo.com.INVALID] > Sent: Saturday, May 14, 2016 9:38 AM > To: Zheng, Kai <kai.zh...@intel.com> > Cc: common-dev@hadoop.apache.org > Subject: Re: Different JIRA permissions for HADOOP and HDFS > > > > On May 14, 2016, at 7:07 AM, Zheng, Kai <kai.zh...@intel.com> wrote: > > > > Hi, > > > > Noticed this difference but not sure if it’s intended. YARN is similar > with HDFS. It’s not convenient. Any clarifying? > > > Under JIRA, different projects (e.g., HADOOP, YARN, MAPREDUCE, > HDFS, YETUS, HBASE, ACCUMULO, etc) may have different settings. At one > point in time, all of the Hadoop subprojects were under one JIRA project > (HADOOP). But then a bunch of folks decided they didn’t want to see the > other sub projects issues so they split them up…. and thus setting the > stage for duplicate code and operational divergence in the source. > > Since people don’t realize or care that they are separate, people > will file INFRA tickets or whatever to change “their project” and not the > rest. This leads to the JIRA projects also diverging… which ultimately > drives those of us who actually look at the project as a whole bonkers. > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org >
