Sorry for being slow about this.
The 'stable' branch is
https://tools.assembla.com/svn/chdk/branches/release-1_0, version number is 1.0.0-<svnrev>
The 'unstable' branch will be the current trunk, version number is 1.1.0-<svnrev> for now.
Ground rules:
* Changes in the 1.0 branch should be bug fixes, or new ports. Efforts should be made to keep the 1.0 autobuild fully functional and the functionality, script and PTP APIs should not change significantly. The version should always be 1.0.x. I don't particularly see any reason to have 1.0.1, 1.0.2 etc for bug fixes, but I'm open to suggestions.
* The trunk should be used for new features, invasive re-writes or experimental stuff. Script, PTP and module APIs may change from version to version in incompatible ways. Anything checked in here should build, and developers should try to keep it usable, but stuff might get broken from time to time. At some point we will have a feature freeze and turn this into the stable release, retiring the previous stable release.
* New ports: The choice of which branch to start with is up to the porter. For people not familiar with CHDK development, starting with stable is probably better. When a port is added, it should be merged into whatever branch it was started from and then backported into the other. If some camera requires major changes outside of the platform area, it should just go in unstable.
* Documentation: We should try to keep documentation for the current stable release as complete as possible. We should also try to document new functionality as we write it. Not sure the best way to do this, but at a minimum try to tag things as in 1.0 or in 1.1. At the moment, we have a lot of "as of build NNNN", with stable versions we should be able to just refer to the release.
Both will be available from the autobuild server. Will update when this is configured.
