Created a ticket for this (hopefully, this was the correct forum). https://issues.apache.org/jira/browse/INFRA-1659
On Thu, Jun 19, 2008 at 11:08 PM, David Reiss <[EMAIL PROTECTED]> wrote: > I chatted with Carl a bit off-list, and it seems that I do not have > access to change this. Does someone want to create an infrastructure > ticket to change our "workflow scheme"? > > --David > > Carl Byström wrote: >> +1 here too. >> >> What kind of access level have you got in JIRA, David? I don't know >> what kind of security Apache impose on their sub-projects in their >> issue tracker. But it's usually a pretty quick fix to add a new >> status. >> >> There should be a link to "Administration" in the top bar, then look >> under Administration -> Issue Settings -> Statuses >> Also, make sure it's part of the workflow the Thrift project has >> chosen/defaulted to. >> >> /Carl >> >> On Thu, Jun 19, 2008 at 8:53 PM, David Reiss <[EMAIL PROTECTED]> wrote: >>> +1 >>> >>> I poked around to try to figure out how to do this, with no luck. >>> Any ideas? >>> >>> --David >>> >>> Kevin Clark wrote: >>>> On Thu, Jun 19, 2008 at 10:07 AM, Bryan Duxbury <[EMAIL PROTECTED]> >> wrote: >>>>> Hey all, >>>>> >>>>> In Hadoop and HBase, there's a status for issues called "Patch >> Available", >>>>> which we use to indicate that the issue has a patch ready to be reviewed >>>>> and/or applied. I think we should make a Patch Available status as >> well as >>>>> an Awaiting Commit status in our Jira. It will make it a lot easier >> to see >>>>> at a glance what state an issue is in. For instance, there are at >> least 3 >>>>> java library issues that had patches on them awaiting review, but you >>>>> wouldn't know that without clicking on each one. >>>> >>>> +1 >>>> >>>> >>>> -- >>>> Kevin Clark >>>> http://glu.ttono.us >>>> >>> >> >
