- From: Seth Chisamore <
>
- To: Alex Soto <
>
- Cc: Chef Dev <
>
- Subject: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] 6/7 Opscode Ticket Triage
- Date: Tue, 7 Jun 2011 19:01:08 -0400
Alex,
We just ran out of time during the weekly ticket triage before we got to
COOK-580. We are currently working through the backlog of resolved/fixed COOK
tickets...using the public "Resolved Cookbook Issues" filter [0] to drive the
meetings. Once we 'catch up' we plan on switching to triaging all new tickets
(that may not even contain a fix) using the public "Untriaged Cookbook
Tickets" filter [1].
Seth
--
Opscode, Inc.
Seth Chisamore, Senior Technical Evangelist
IRC, Skype, Twitter, Github: schisamo
[0]
http://tickets.opscode.com/secure/IssueNavigator.jspa?requestId=10474
[1]
http://tickets.opscode.com/secure/IssueNavigator.jspa?requestId=10472
On Tuesday, June 7, 2011 at 6:43 PM, Alex Soto wrote:
>
I flagged one as fixed a while back
>
(http://tickets.opscode.com/browse/COOK-533) and just re-assigned to Seth
>
(was Joshua). Sorry for the noise Seth, but I'm emailing the list in case
>
you don't get emails from JIRA.
>
>
Alex
>
>
On Jun 7, 2011, at 3:36 PM, Bryan McLellan wrote:
>
> On Tue, Jun 7, 2011 at 3:15 PM, Seth Chisamore
>
> <
>
>
>
> (mailto:
)>
>
> wrote:
>
> > COOK-580 wasn't picked up since it is still marked 'Opened'. :)
>
>
>
> Right, as Seth indirectly noted, we only merge tickets that are marked
>
> fixed/resolved, otherwise we don't know what tickets have fixes. Once
>
> we merge them, we then set them to fixed/closed.
>
>
>
> I updated the "How To Contribute Page" recently to make the current
>
> process a little clearer. If it isn't clear to anyone, please let me
>
> know.
>
>
>
> http://wiki.opscode.com/display/chef/How+to+Contribute
>
>
>
> Bryan
Archive powered by MHonArc 2.6.16.