> So Subversion 1.3.0RC4 is out, which means the 1.3.0 release isn't
> that far away anymore. It's time to think about the next TSVN release.
I didn't release any new 1.2.x 64-bit builds under the impression
SVN 1.3 would be released "Real Soon Now"(tm) ;)
> * change the build to use VS.NET2005 (that also means that people
> using the free VC-Express can build TortoiseBlame, SubWCRev, ResText,
> ... without any problems)
Great! Things will be much easier for me then. Could you please
keep me informed as soon as the project files have been converted?
> * Maybe even get it to build for 64-bit
That will depend on whether the SVN projects can be patched automatically.
For the TSVN projects, we just need to check how the additional, unknown
platform (x64) is handled by VC-Express.
> Then, when Subversion 1.3.0 gets released:
> * create a branch from trunk, named "1.3.x".
Perhaps, we should wait (just as an additional constraint) until we
are sure about the VC2k5 port (i.e. no unforseen obstacles arise) and
have decided about the x64 integration. (Please note, that VC2k5 does
not depend on the x64 issue.)
Since both changes are neither trivial nor "bugfix only", they should
not take place on 1.3.x but on the trunk. If they are ready before 1.3.x
gets branched they will be available in 1.3. Otherwise, they have to
wait for 1.4.
> * release an RC1 from that branch
> * wait a week to give people time to test RC1
> * fix bugs found in RC1, merge them back to 1.3.x
> * if fixedbugsinRC > 3 OR peoplerequestinganotherRC goto -3
> * release 1.3.0
> Keep working on trunk, implementing new features. But 1.3.x releases
> will be made from the 1.3.x branch, not from trunk anymore. And they
> will *only contain bugfixes*, no new features or other changes.
Received on Wed Nov 30 16:45:45 2005