Hi, I think we'll have to think on the mac situation later. There's really way too much to test properly over the different versions to fix quickly. I'll come up with a test plan for OSX and gather together reasons for not supporting various combinations. (eg. whl on 32bit). As you say packaging can come after the release. Some of the breakages for macOS require fixes in SDL, and packaging for 32bit requires much other work (seems whl doesn't work, so a .dmg could possibly be made again).
I updated the milestones for those issues. I think you should now be able to modify milestones in bitbucket. Let's just assign milestones to things we do going forwards, and clean up the other ones as they are done. Next from that list of mine... I'll work on updating the release notes. I thought I had an issue open already for that... but can't find it right now. cheers, On Tue, Jan 10, 2017 at 8:17 PM, Thomas Kluyver <tak...@gmail.com> wrote: > On 10 January 2017 at 00:21, René Dudfield <ren...@gmail.com> wrote: > >> The mac problems are pretty severe... I'm looking into them right now. >> Maybe we can roll back some of the changes fairly easily, because it was >> working at least on the macs I tested with before the pre- release. > > > Could it be that it's the wheels that are the problem, and when you tested > the pre-release you installed from source? If the Mac wheel builds aren't > working, maybe we should do a release without them and leave it up to > downstream packagers (like Homebrew and Macports) to provide precompiled > packages for Macs. > > > There's a few items still open in the 1.9.3 milestone. Let's set them to > another milestone if we're not going to do them. > > There are a bunch still open in the 1.9.2 milestone. I don't think I have > the ability to create new milestones, nor to change milestones for more > than one issue at once. > > Thomas > <https://bitbucket.org/pygame/pygame/issues?milestone=1.9.3> >
