Re: [Python-Dev] tracker status options

2009-03-25 Thread Nick Coghlan
Daniel (ajax) Diniz wrote: I feel we should make the tracker more useful for core developers, volunteers and end-users. I also think having a clear workflow helps a lot. Yet, I'd rather have a tracker that allowed users with different interpretations to work as they feel most comfortable than

[Python-Dev] tracker status options

2009-03-24 Thread R. David Murray
On Tue Mar 24 02:06:29 CET 2009, Tennessee Leeuwenburg tleeuwenburg at gmail.com wrote: Perhaps some developers have a well-established workflow and interpret these flag in a particular, consistent fashion, however part of the purpose of the issue tracker is to allow a diverse group to work on

Re: [Python-Dev] tracker status options

2009-03-24 Thread Terry Reedy
R. David Murray wrote: So, having triaged a few issues, here are my thoughts. The current workflow is roughly: o test needed o patch needed o patch review o commit review One can look at these and see what needs to be done next. I think that in practice the above list

Re: [Python-Dev] tracker status options

2009-03-24 Thread Martin v. Löwis
o consensus needed o test needed o patch needed o patch needs work o patch review o commit review The first of these additional items is equivalent to your bullet item above. I would propose that the issue, regardless of whether or not it is a bug fix or a

Re: [Python-Dev] tracker status options

2009-03-24 Thread R. David Murray
On Tue, 24 Mar 2009 at 21:27, Martin v. L?wis wrote: o consensus needed o test needed o patch needed o patch needs work o patch review o commit review The first of these additional items is equivalent to your bullet item above. I would propose that the issue,

Re: [Python-Dev] tracker status options

2009-03-24 Thread Martin v. Löwis
So, 'confirmed' instead of 'consensus needed' (or confirmed/approved, to cover feature requests), and 'patch is appropriate' that comes...I'm not quite sure where? If the person who did the triage actually thinks the patch is ready to be committed, it would be commit review. Not sure in what

Re: [Python-Dev] tracker status options

2009-03-24 Thread R. David Murray
On Tue, 24 Mar 2009 at 22:41, Martin v. L?wis wrote: If the person doing the triage has made a final call, the issue can enter the next stage. There should never be debate on the tracker, IMO (although there often is). It might be that people disagree with a triage, then they should appeal to

Re: [Python-Dev] tracker status options

2009-03-24 Thread Martin v. Löwis
OK, so given this then I revise the way I understand what is happening in the ticket I'm looking at: a reviewer has said this patch needs work and the submitter has not responded. Since the behavior has been accepted as a valid bug this means...I can either work on the patch, or post a

Re: [Python-Dev] tracker status options

2009-03-24 Thread Daniel (ajax) Diniz
R. David Murray wrote: I understood from posts I saw go by earlier from Daniel that 'pending' meant 'close pending unless there is feedback to the contrary' (and I just used it that way).  It sounds like that is indeed correct but not universally known, and thus I would suggest that at a

Re: [Python-Dev] tracker status options

2009-03-24 Thread Ron Adam
Tennessee Leeuwenburg wrote: Hi all, I'm continuing to (slowly) work through issues. I have been looking particularly at a lot of the open issues regarding strftime. It would be great to put in some of those extra status options that were discussed recently... Open/New Needs help

Re: [Python-Dev] tracker status options

2009-03-24 Thread Tennessee Leeuwenburg
Hi Ron, Good flowchart. Cheers, -T On Wed, Mar 25, 2009 at 1:11 PM, Ron Adam r...@ronadam.com wrote: Tennessee Leeuwenburg wrote: Hi all, I'm continuing to (slowly) work through issues. I have been looking particularly at a lot of the open issues regarding strftime. It would be great

Re: [Python-Dev] tracker status options

2009-03-24 Thread Steve Holden
R. David Murray wrote: On Tue, 24 Mar 2009 at 21:27, Martin v. L�wis wrote: o consensus needed o test needed o patch needed o patch needs work o patch review o commit review The first of these additional items is equivalent to your bullet item above. I would

Re: [Python-Dev] tracker status options

2009-03-23 Thread Brett Cannon
2009/3/22 Tennessee Leeuwenburg tleeuwenb...@gmail.com Hi Daniel, That would be great. It occurs to me that if we wanted to use Stage settings, it would be easy to search for issues which are not closed by literally searching for 'not closed' rather than 'open'. I think it's also unclear

Re: [Python-Dev] tracker status options

2009-03-23 Thread Martin v. Löwis
That would be great. It occurs to me that if we wanted to use Stage settings, it would be easy to search for issues which are not closed by literally searching for 'not closed' rather than 'open'. I think it's also unclear whether the 'pending' stage means 'suspended

Re: [Python-Dev] tracker status options

2009-03-23 Thread Tennessee Leeuwenburg
On Tue, Mar 24, 2009 at 11:00 AM, Martin v. Löwis mar...@v.loewis.dewrote: That would be great. It occurs to me that if we wanted to use Stage settings, it would be easy to search for issues which are not closed by literally searching for 'not closed' rather than 'open'. I

Re: [Python-Dev] tracker status options

2009-03-23 Thread R. David Murray
On Mon, 23 Mar 2009 at 16:20, Tennessee Leeuwenburg wrote: literally searching for 'not closed' rather than 'open'. I think it's also unclear whether the 'pending' stage means 'suspended pending additional user feedback' or 'resolution of this issue is impending'. My understanding was that it

Re: [Python-Dev] tracker status options

2009-03-22 Thread Tennessee Leeuwenburg
Hi Daniel, That would be great. It occurs to me that if we wanted to use Stage settings, it would be easy to search for issues which are not closed by literally searching for 'not closed' rather than 'open'. I think it's also unclear whether the 'pending' stage means 'suspended pending additional

Re: [Python-Dev] tracker status options

2009-03-19 Thread Martin v. Löwis
It would be great to put in some of those extra status options that were discussed recently... Open/New Needs help / Chatting Under development Pending feedback Closed Are you sure that you want them to be status options? Why not stages? ISTM that an issue that Needs help

Re: [Python-Dev] tracker status options

2009-03-19 Thread Brett Cannon
On Wed, Mar 18, 2009 at 23:47, Martin v. Löwis mar...@v.loewis.de wrote: It would be great to put in some of those extra status options that were discussed recently... Open/New Needs help / Chatting Under development Pending feedback Closed Are you sure that you

Re: [Python-Dev] tracker status options

2009-03-19 Thread Martin v. Löwis
On Wed, Mar 18, 2009 at 23:47, Martin v. Löwis mar...@v.loewis.de mailto:mar...@v.loewis.de wrote: It would be great to put in some of those extra status options that were discussed recently... Open/New Needs help / Chatting Under development

Re: [Python-Dev] tracker status options

2009-03-19 Thread Daniel (ajax) Diniz
Martin v. Löwis wrote: In addition, I would like to see a specification of the exact labels to be used, plus a one-line description that should be attached to the labels. Tennessee, If you'd like to test those additional status options, I'm setting a test instance of the Python tracker up at

[Python-Dev] tracker status options

2009-03-18 Thread Tennessee Leeuwenburg
Hi all, I'm continuing to (slowly) work through issues. I have been looking particularly at a lot of the open issues regarding strftime. It would be great to put in some of those extra status options that were discussed recently... Open/New Needs help / Chatting Under development