Release plan

Hi,

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.

My plan (subject to change, please comment!):

* get the cache to a state where Peter is ok with it (hmmm - maybe
we'd have to make the release earlier, people might get angry if we
don't release for another two years ;)
* 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)
* Maybe even get it to build for 64-bit

Then, when Subversion 1.3.0 gets released:
* create a branch from trunk, named "1.3.x".
* 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.

Comments?

Stefan

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org