After working on this for a day, here is my idea of what needs to be done = Pyglet 1.2 Release To Do =
== High priority == * merge cocoa port, i.e. hg+https://code.google.com/r/evilphillip-cocoa-ctypes2/ * Create a release checklist so anyone can help. E.g. * See if we have test coverage on major platforms and it passes. Ask for testers if needed. * Write readme * Create the packages - .zip/tgz? .dmg/msi? easy_install/pip? * submit the packages to pypi? or publish on website? * update website with new docs. * Release 1.2_RC_1 -- no need to get it perfect before releasing. * write README (s) how is pyglet 1.2 different from 1.1? * support 64bit Python * write ANNOUNCEMENT (s) what's new? * Get docs working, either epydoc or switch to Sphinx * fix epydoc * add an issue to tracker * Release 1.2_RC_2 * There are some patches in the issue tracker that seem worthwhile such as http://code.google.com/p/pyglet/issues/detail?id=482 * More releases... == Medium Priority == * Make it easier for people to submit unit-test results on different platforms so that we have more confidence that changes are good. * Page describing testing process -- e.g. it can take an hour * Have a place to submit testing results and have it summarized, e.g. tests passed, tests failed, what platform, python version, commit # * Let people see what areas have been tested and what areas need testing. * Let people test just a section of the test plan (the whole thing can take an hour) and submit it. * Make output of test runner easier to use, i.e. easy to send to us and easy to summarize. * update web site * move web site to Bitbucket * create group 'pyglet' * add repository pyglet.bitbucket.org (see https://confluence.atlassian.com/display/BITBUCKET/Publishing+a+Website+on+bitbucket) * add CNAME for pyglet.org to pyglet.bitbucket.org (I am not sure, but it should work) * mention 1.2 * direct link to Google Code from top menu * update Contribute to be clear * send patches * site in repository is broken http://code.google.com/p/pyglet/source/browse/#hg%2Fwebsite * write instructions / fix it to work from checkout. (s) Richard needs time * update wiki pages * draw a line on http://code.google.com/p/pyglet/wiki/ReleaseSchedule * integrate patches (s) Richard * update issue tracker * add website label to issue tracker * allow users to assign labels when creating new issues * add 1.2 milestone (s) Richard == Low Priority == * build a windows installer -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
