My daytime job is writing cross-platform code in Python; I'm happy to help out with either Windows, Linux or Mac builds.
On 1 August 2018 at 04:54, Luke Paireepinart <rabidpoob...@gmail.com> wrote: > Sounds reasonable to major version up with SDL. Is there a sponsor on the > list for the windows builds of pygame? If not, I would love to volunteer > for this. > > > On Tue, Jul 31, 2018, 7:29 AM René Dudfield <ren...@gmail.com> wrote: > >> So. I've been thinking how to have SDL2 and SDL1 releases on pypi at the >> same time. >> >> 1.9.5.devX releases, with SDL1 being compiled in. >> 2.0.0.devX releases, using SDL2 stuff. >> >> The benefit is that we can: >> >> - 'release early, release often'. The fact is most people only test, >> or try things out once things are released. >> - we need help testing a SDL2 pygame, and having it on pypi makes >> that easy for people. My guess is only 2-3 people have tried the SDL2 >> branch so far for example. >> - there's only one tree, which is easier to maintain than separate >> branches. >> - we also need help testing SDL1 stuff, to make sure it hasn't broken. >> >> >> >> *Step 1.* >> The first step is to get the continuous releases working, and I'll reset >> the version number in git master to 1.9.5.dev0 >> Each merge into master will do a release to pypi as 1.9.5.devX, where X >> is the number of commits since the last release tag (1.9.4). >> >> >> *Step 2.* >> Unfortunately I don't see a way to merge the SDL2 branch in incrementally. >> So I'll do a big merge of the SDL2 stuff into master. >> With SDL1 being the default. >> >> *Step 3.* >> Do the repo files cleanup (mentioned earlier). >> >> >> *Step 4.* >> Get pygame 2 working on non-linux platforms. >> Get continuous deploys working for pygame 2.0.0.devX. >> >> *Step 5.* >> There will be a pygame 1.9.5 release with the API cleanup, and disabled >> SDL2 support. >> Including other platform fixes (like how *BSD pygame is broken currently). >> >> >> So, that's the plan. >> >
