* Update README.txt and doc/BuildXXX.txt to point to the latest required
-* Make sure, all tests for all supported Python versions work.
+* Make sure, all tests for all supported Python versions work on all
Once anything's tested, updated written down, the required packages have to be
+built. First of all, the source packages are required as the binary packages
+will be built using them. ::
+This also will create a set of bundled docs to be distributed.
+For Win32 platforms, binary builds (MSI packages) for the Python versions
+*2.4*, *2.5*, *2.6* and *3.0* have to be made, based on one of the source
+packages, which were just created. ::
+ c:\PythonXX\python.exe setup.py build bdist_wininst
+ c:\PythonXX\python.exe setup.py build bdist_msi
+Once all installers are available, make sure they work and ship anything
+required by running the unit tests: ::
+ # Win32 CMD prompt (do that for all versions):
+ c:\PythonXX\python.exe -c "import pygame2.test; pygame2.test.run ()"
+*TODO: Instructions for Mac OS X platforms*
+Once all packages are built the revision control tree can be tagged with the
+new version, the packages be published and an announcement sent to the mailing
likely to fail and the user will blame either the developer or the library.
With a consistent versioning scheme, developers can test against versions
-explicitly to guarantee the functionality with those. User can receive an
+explicitly to guarantee the functionality with those. User can receive an
explicit notice, if their installed version might be incompatible and react