[Python-Dev] Summary of Python tracker Issues (original) (raw)
Ezio Melotti ezio.melotti at gmail.com
Fri Mar 1 02:05:55 EST 2019
- Previous message (by thread): [Python-Dev] Update from the Python Steering Council about CPython Development
- Next message (by thread): [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy <tjreedy at udel.edu> wrote:
On 2/28/2019 6:54 PM, Glenn Linderman wrote: > There seems to be enough evidence that something went wrong somewhere, > though, and whoever maintains that process should start investigating, > but it would still be nice to get confirmation from a non-Google email > recipient whether they did or did not get the Summary messages. > > I wonder if there is a way to manually send them, and if the missing two > weeks of activity can be reported... once the sending problem is > understood and resolved. I posted a note to the core-workflow list, but I don't know if anyone with power or knowledge still reads it.
The tracker got migrated recently, and that's the most likely cause of the missing reports. We'll look into it and get them back :)
To get a listing, go to the tracker search page, put 2019-02-09 to 2019-03-01 in the date box, and change status to don't care. At the moment, this returns 204 issues.
-- Terry Jan Reedy
- Previous message (by thread): [Python-Dev] Update from the Python Steering Council about CPython Development
- Next message (by thread): [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]