[pyglet.wiki] push by - Edited wiki page RoadMap12 through web user interface. on 2014-05-31 16:58 GMT

[pyg...@googlecode.com]

Revision: 6681003e9237
Branch: default
Author: useb...@gmail.com
Date: Sat May 31 16:58:35 2014 UTC
Log: Edited wiki page RoadMap12 through web user interface.
http://code.google.com/p/pyglet/source/detail?r=6681003e9237&repo=wiki

Modified:
/RoadMap12.wiki

=======================================
--- /RoadMap12.wiki Fri Jun 29 08:20:03 2012 UTC
+++ /RoadMap12.wiki Sat May 31 16:58:35 2014 UTC
@@ -1,67 +1,29 @@
#summary The roadmap for the 1.2 release.
#labels Featured

+ * ~~1.2 Alpha 1~~
+ * 1.2 Beta 1
+ * 1.2 RC 1
+ * 1.2
+
= Pyglet 1.2 Release To Do =
+ * See if we have test coverage on major platforms and it passes. Ask for
testers if needed.
+ * Review the README.
+ * Update the CHANGELOG.
+ * write ANNOUNCEMENT (s) what's new?
+ * Create the packages: source .zip and tgz; installers as .dmg/msi;
ensure pip compatibility.
+ * Submit the packages to PyPI and use PyPI Javascript hook to display
download box.
+ * Update website making dev docs main docs.

== High priority ==
- * ~~merge Philip's
[hg+https://code.google.com/r/evilphillip-cocoa-ctypes2/ cocoa port]~~
- * 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: source .zip and tgz; installers as .dmg/msi;
ensure pip compatibility.
- * submit the packages to PyPI and use PyPI Javascript hook to display
download box
- * update website with new docs.
- * Apply submitted patches:
- * ~~Txema Vicente's
[http://code.nabla.net/doc/pyglet/pyglet_sphinx_patch.zip sphinx patch]~~
- * ~~issue 580 from M Paola for DDS_RGBA_DXT1_LOAD and similar tests~~
- * ~~fix multiline/wrap lines issue 394 - M Paola~~
- * apply issue 482?
- * ~~Update CHANGELOG~~
- * Release *1.2 alpha 1* -- no need to get it perfect before releasing.
- * write README (s) how is pyglet 1.2 different from 1.1?
- * supports 64bit Python (on which? all? platforms)
- * try to get Python 3 supported
- * write ANNOUNCEMENT (s) what's new?
- * ~~Get docs working, either epydoc or switch to Sphinx~~
- * fix website build scripts
- * Review the issue tracker
- * Release *1.2 beta 1*
- * More releases...
-
-
-== Medium Priority ==
- * Look at these patches:
- * Issue 387 - select input events on Linux.
- * Issue 371 - float positions for sprite
- * Issue 532 - No Core Profile support on OS X 10.7 Lion
-
- * 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
-
+ * Fix
[https://code.google.com/p/pyglet/issues/list?q=label:1.2-release-blocker
1.2 release blockers]
+ * Check 64-bit Python support (on which? all? platforms)
+ * Review Python 3 support
* 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