I think we should rotate who does the release... so more people can get the hang of it, and so we can better document it as we go.
Any volunteers to be the next release manager? We can guide whoever it is through the processes (and document the bits that aren't documented) Things for the next release I've seen so far... FIXED - source tar ball. https://bitbucket.org/pygame/pygame/issues/319/missing-versionpyin-in-source-tarball - release notes release summary, and updating WHATSNEW, posting news on the website blog, twitter, reddit - document build system All the new stuff with travisci etc needs a document for them. (These two probably shouldn't stop a release.) - macOS/OSX issues https://bitbucket.org/pygame/pygame/issues/320/wont-start-on-mac-os-x-10122-on-python-352 32bit support needed again - python 3.6 testing, releases https://bitbucket.org/pygame/pygame/issues/321/test-on-and-make-packages-for-python-36The source tar ball needs to go The source tar ball should be put Into the /ftp/ folder on the web, since some of the distros look there for updates. On Sun, Dec 25, 2016 at 6:29 PM, DiliupG <dili...@gmail.com> wrote: > thanks rene! Merry Christmas! :) > > On Sun, Dec 25, 2016 at 3:35 PM, Thomas Kluyver <tak...@gmail.com> wrote: > >> Welcome back, René! +1 to doing a 1.9.3 release soon. Do you see how to >> get wheels for the various platforms? I'm happy to help build them again, >> but it won't be today. >> >> Have a good Christmas, everyone! >> >> Thomas >> >> On 24 Dec 2016 11:43 p.m., "René Dudfield" <ren...@gmail.com> wrote: >> >>> Hello, >>> >>> we need to do a quick 1.9.3 release because of the source tar ball being >>> broken for 1.9.2. I don't think this should wait for other issues like >>> python 3.6 updates or such. >>> >>> Sound like a plan? >>> >> > > > -- > Kalasuri Diliup Gabadamudalige > > https://dahamgatalu.wordpress.com/ > http://soft.diliupg.com/ > http://www.diliupg.com > > ************************************************************ > ********************************** > This e-mail is confidential. It may also be legally privileged. If you are > not the intended recipient or have received it in error, please delete it > and all copies from your system and notify the sender immediately by return > e-mail. Any unauthorized reading, reproducing, printing or further > dissemination of this e-mail or its contents is strictly prohibited and may > be unlawful. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > ************************************************************ > ********************************** > >
