On Thu, May 8, 2008 at 5:03 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > So there was a release critical issue open about making sure to update > Py3k's RELNOTES file. I've updated the release script so that I'll be sure > to edit this file, however I'm not sure what the policy is on updating it. > Would you expect me to update it and if so, from what data source? Do we > list all open critical bugs on the Py3k tracker? All open PEPs? > > I'd like to ask everyone doing Py3k development to help pitch in and keep > this file up-to-date. I think this will be more important as we move to > beta releases starting next cycle.
I believe I invented this file for the 3.0a1 release, when I realized that some things were broken but I didn't want to hold up the release any longer. I also kept adding to it for a while *after* the release, which seems odd, except that I also copied the updated contents to the website. Possibly making it public on the website is the main goal of the file -- it makes users aware of the top ten (say) "gotchas" without having to scan the bug tracker or ask the mailing list. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
