On Sat, 22 Oct 2005, Jim Gallacher wrote:
Alternative 1 - no version changes get committed to trunk:
Alternative 2 - two version changes get committed to trunk:
I think neither one is right. I should be:
svn co $URL/trunk trunk
cd trunk
(Change the MPV_STRING to "3.2.xb")
svn ci -m "changed version in trunk"
# note the next line uses remote urls
svn copy $URL/trunk $URL/tags/release-3-2-xb
# note "export" not "co"
svn export $URL/tags/release-3-2-xb mod_python-3.x.x
The "export" command above should produce a clean set of files where you
should not need to make any changes and be able to just tar it as is
(well, except for the html documentation step).
Nicolas's SQLiteSession.py is still there, but it's the only experimental
stuff. Perhaps we should create a new experimental branch, or have
individual branches for messing around.
Yep, I'm thinking we should try to keep the trunk closest to the
official/current version and a branch for new experimental stuff.
SQLiteSession should definitely not be included in the tarball.
Grisha
