In article <lfmbjj$nka$2...@ger.gmane.org>, Georg Brandl <g.bra...@gmx.net> wrote:
> Am 11.03.2014 06:31, schrieb Ned Deily: > > In article > > <cadisq7eif2ybkwr4nqlxi800crqzwwvzms11enmt0pqna23...@mail.gmail.com>, > > Nick Coghlan <ncogh...@gmail.com> wrote: > >> On 11 March 2014 11:29, R. David Murray <rdmur...@bitdance.com> wrote: > >> > The whatsnew updates (including the one for help) weren't copied into > >> > rc3. They will be in final though, unless Larry forgets. > >> > >> Oh, cool - yes, it will be good to have an up to date What's New > >> shipped, especially as part of the compiled Windows docs. > > > > I was going to bring that point up today. How are all the new whatsnew > > updates going to get into the 3.4.0 release? They've, correctly, been > > being pushed to the default branch. But, AFAIK, for them to show up in > > the 3.4.0 released docs we ship, all of the doc changes are going to > > need to be cherry picked (or a big mass diff from the default branch) > > into the 3.4 release branch, otherwise they will not be part of the > > release. (They certainly won't be part of the docs included with the > > installers I build unless they are in the 3.4 releasing branch.) > > Copying the file from default and doing just one commit in the releasing > branch should be the easiest way. That covers the whatsnew file but the changes RDM have been making affect other parts of the documentation and Misc/NEWS, too. -- Ned Deily, n...@acm.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
