Re: [Python-Dev] Tracker status

On Tue, 03 Aug 2010 20:36:36 +0200, Georg Brandl wrote: > Am 03.08.2010 19:05, schrieb Brian Curtin: > > On Tue, Aug 3, 2010 at 11:58, R. David Murray > > Fixed. Apparently a line was dropped when applying a patch to > > the tracker, but the mistake didn't surface until roundup > >

Re: [Python-Dev] Tracker status

Am 03.08.2010 19:05, schrieb Brian Curtin: > On Tue, Aug 3, 2010 at 11:58, R. David Murray Fixed. Apparently a line was dropped when applying a patch to > the tracker, but the mistake didn't surface until roundup > was restarted after the reboot. > > -- > R. David Murray

Re: [Python-Dev] Tracker status

On Tue, Aug 3, 2010 at 11:58, R. David Murray wrote: > On Tue, 03 Aug 2010 16:35:01 +0200, Antoine Pitrou > wrote: > > Apparently you are not the only one experiencing it. > > On #python-dev we get such notifications: > > > > alanwilter roundup * #9485/signal.signal/signal.alarm not > > working

Re: [Python-Dev] Tracker status

On Tue, 03 Aug 2010 16:35:01 +0200, Antoine Pitrou wrote: > Apparently you are not the only one experiencing it. > On #python-dev we get such notifications: > > alanwilter roundup * #9485/signal.signal/signal.alarm not > working as expected: [new] I have this example code to illustrate a > probl

Re: [Python-Dev] Tracker status

Apparently you are not the only one experiencing it. On #python-dev we get such notifications: alanwilter roundup * #9485/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... alanwilter roundup * #9486/signal.signal/signal.alarm not

Re: [Python-Dev] Tracker status

There's no new issue posted this morning. I tried to post an issue, and an error occurred on submit. So... -- Florent 2010/8/3 Fred Drake > On Tue, Aug 3, 2010 at 1:01 AM, Ray Allen wrote: > > Is the tracker OK now? > > It's working for me. > > > -Fred > > -- > Fred L. Drake, Jr. > "A

Re: [Python-Dev] Tracker status

On Tue, Aug 3, 2010 at 1:01 AM, Ray Allen wrote: > Is the tracker OK now? It's working for me.   -Fred -- Fred L. Drake, Jr.    "A storm broke loose in my mind."  --Albert Einstein ___ Python-Dev mailing list Python-Dev@python.org http://mail.python

Re: [Python-Dev] Tracker status

On Tue, Aug 3, 2010 at 07:01, Ray Allen wrote: > Is the tracker OK now? Works for me. Cheers, Dirkjan ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/opt

Re: [Python-Dev] Tracker status

Is the tracker OK now? -- Ray Allen Best wishes! ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Tracker status

Down for me as well. Initially I though it was shield by "Great Firewall" since I'm from China. On Tue, Aug 3, 2010 at 9:29 AM, David Stanek wrote: > On Mon, Aug 2, 2010 at 6:17 PM, Nick Coghlan wrote: > > Are the bug tracker and meta-tracker down for anyone else, or is it just > me? > > > > It

Re: [Python-Dev] Tracker status

On Mon, Aug 2, 2010 at 6:17 PM, Nick Coghlan wrote: > Are the bug tracker and meta-tracker down for anyone else, or is it just me? > It is down for me as well. It appears to be accepting the connection and then just doesn't return any content. -- David blog: http://www.traceback.org twitter: ht

[Python-Dev] Tracker status

Are the bug tracker and meta-tracker down for anyone else, or is it just me? Cheers, Nick. -- Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/pyth

Re: [Python-Dev] tracker status options

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 th

Re: [Python-Dev] tracker status options

"Martin v. Löwis" writes: > > 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 i

Re: [Python-Dev] tracker status options

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 bull

Re: [Python-Dev] tracker status options

Hi Ron, Good flowchart. Cheers, -T On Wed, Mar 25, 2009 at 1:11 PM, Ron Adam 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

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 hel

Re: [Python-Dev] tracker status options

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 mi

Re: [Python-Dev] tracker status options

> 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

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 p

Re: [Python-Dev] tracker status options

> 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 wh

Re: [Python-Dev] tracker status options

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, regardle

Re: [Python-Dev] tracker status options

> 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 o

Re: [Python-Dev] tracker status options

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 actua

[Python-Dev] tracker status options

On Tue Mar 24 02:06:29 CET 2009, Tennessee Leeuwenburg 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 development as a group. On

Re: [Python-Dev] tracker status options

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 mea

Re: [Python-Dev] tracker status options

On Tue, Mar 24, 2009 at 11:00 AM, "Martin v. Löwis" wrote: > > 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

Re: [Python-Dev] tracker status options

> 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/3/22 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 'pend

Re: [Python-Dev] tracker status options

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 additiona

Re: [Python-Dev] tracker status options

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

Re: [Python-Dev] tracker status options

> On Wed, Mar 18, 2009 at 23:47, "Martin v. Löwis" > wrote: > > > It would be great to put in some of those extra status options > that were > > discussed recently... > > > >"Open/New" > >"Needs help / Chatting" > >"Under developm

Re: [Python-Dev] tracker status options

On Wed, Mar 18, 2009 at 23:47, "Martin v. Löwis" 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

Re: [Python-Dev] tracker status options

> 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

[Python-Dev] tracker status options

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"