Oddity in MISC/News on default
Hello, In 3.4's Misc/NEWS, there's a huge section entitled "What's New in Python 3.3.1 release candidate 1". It seems it shouldn't be there, should it? Regards Antoine.
Why not? Presumably those news items were all merged into the default branch, and Misc/NEWS also has all the news for all 3.3.0 releases. Why pick on 3.3.1 rc1? On Thu, Jul 4, 2013 at 12:09 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Hello,
In 3.4's Misc/NEWS, there's a huge section entitled "What's New in Python 3.3.1 release candidate 1". It seems it shouldn't be there, should it?
Regards
Antoine.
_______________________________________________ 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/guido%40python.org
-- --Guido van Rossum (python.org/~guido)
Le jeudi 04 juillet 2013 à 12:17 -0700, Guido van Rossum a écrit :
Why not? Presumably those news items were all merged into the default branch, and Misc/NEWS also has all the news for all 3.3.0 releases. Why pick on 3.3.1 rc1?
3.3.1rc1 is the only post-3.3.0 release that's mentioned there (e.g. 3.3.2 isn't), which is what makes me thing a mistake was made along the way (probably when merging). Regards Antoine.
Maybe the mistake is that the others aren't mentioned? Or perhaps everything before 3.4a1 should be dropped? I forget what kind of policy we have for this -- is it all changes in this branch or only changes unique to this branch? On Thu, Jul 4, 2013 at 12:19 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Le jeudi 04 juillet 2013 à 12:17 -0700, Guido van Rossum a écrit :
Why not? Presumably those news items were all merged into the default branch, and Misc/NEWS also has all the news for all 3.3.0 releases. Why pick on 3.3.1 rc1?
3.3.1rc1 is the only post-3.3.0 release that's mentioned there (e.g. 3.3.2 isn't), which is what makes me thing a mistake was made along the way (probably when merging).
Regards
Antoine.
_______________________________________________ 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/guido%40python.org
-- --Guido van Rossum (python.org/~guido)
On 7/4/2013 3:36 PM, Guido van Rossum wrote:
Maybe the mistake is that the others aren't mentioned? Or perhaps everything before 3.4a1 should be dropped? I forget what kind of policy we have for this -- is it all changes in this branch or only changes unique to this branch?
It cannot be 'unique' because most bug fixes are not unique to any branch. News for 3.x should have all relevant changes to 3.x, and, I think, only those. The question is whether the entries under 3.3.1rc1 in 3.4 News are changes unique to 3.3.1rc1 that should not be in News 3.4; changes to both 3.3 and 3.4 that are now listed twice, and should only be listed once; or changes to 3.4 that are now listed only under 3.3 but should instead be listed as 3.4 changes. I am not looking at the moment because is it 3am here. -- Terry Jan Reedy
Does annotate show it might have been added accidently in a merge? 2013/7/4 Antoine Pitrou <solipsis@pitrou.net>:
Hello,
In 3.4's Misc/NEWS, there's a huge section entitled "What's New in Python 3.3.1 release candidate 1". It seems it shouldn't be there, should it?
Regards
Antoine.
_______________________________________________ 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/benjamin%40python.org
-- Regards, Benjamin
participants (4)
-
Antoine Pitrou -
Benjamin Peterson -
Guido van Rossum -
Terry Reedy