On Wed, 28 Mar 2012 20:56:30 -0000, "Jason R. Coombs" <jar...@jaraco.com> wrote: > Will the release notes include something about this change, since it will > likely have broad backward incompatibility for all existing virtualenvs? I > wouldn't expect someone in operations to read the virtualenv news to find > out what things a Python upgrade will break. Indeed, this update will > probably be pushed out as part of standard, unattended system updates.
I think it is reasonable to put something in the release notes. This change is much larger than changes we normally make in maintenance release, because it fixes a security bug. But because it is larger than normal, adding release notes like this about known breakage is, I think, a good idea. Perhaps you and Carl could collaborate on a page explaining the issue in detail, and on a brief note to include in the release notes that points to your more extensive discussion? But keep in mind I'm not the release manager; we'll need their buy in on this. --David _______________________________________________ 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
