Versioning?

We have two seperate libraries, Ogre and CEGUI that we are binding. We should really look into the issue of versioning.

Right now, releases are done based on Ogre:
PyOgre-1.0.4-0
PyOgre-1.0.4-1

PyOgre-1.0.5-0
PyOgre-1.0.5-1
PyOgre-1.0.5-2

However, these could include any of CEGUI. I'm thinking we may need to split installation/versioning of the libraries. So that for windows there would be an installer for PyOgre and for PyCEGUI:
PyOgre-1.0.5-3 <--- only files for pyogre
PyCEGUI-0.4.0-0 <--- only files for cegui

We would also make changes to the repository. Trunk would remain the same (development for the current version of whatever library we are working with). However, we would start adding tags for different CEGUI/Ogre versions after we version bump. For example, lets say CEGUI went from 0.4.0 to 0.5.0. Before upgrading we would commit a tag to tags/cegui-0.4.0 which contained only the trunk/pyogre/cegui folder. The same goes for Ogre version bumps.

Does this sound reasonable?

Sounds reasonable. Will you be providing seperate installation packages for say python2.3 and python2.4. Also what about the data files, for example CEGUI's datafiles appear more upto date than Ogre's.

Yup, that sounds good.

Sounds reasonable. Will you be providing seperate installation packages for say python2.3 and python2.4. Also what about the data files, for example CEGUI's datafiles appear more upto date than Ogre's.
I plan on having a python2.3 and 2.4 release.

As far as datafiles, I want to use CEGUI's current datafiles (for the media/ directory), but I can't do that until I have the current testcegui*.py updated to use the most recent media.