David Abrahams wrote:
on Mon Aug 27 2007, "Johan Nilsson" <r.johan.nilsson-AT-gmail.com> wrote:
Michael Caisse wrote:
Johan Nilsson wrote:
As I understood it, there will be a single "relase candidate" _branch_, used for the "ever-available stable build". The individual release candidates would still need to be separately tagged for "official" release candidates.
Release candidates are a *branch/copy* :
http://svn.boost.org/trac/boost/wiki/ImprovingPractices#Releasetags
and my assumption from reading is that they are locked when made available as a *release*.
If that's the case, I stand corrected. Doesn't really make sense to put them under "tags" if they are branches, though.
You make a release branch, then you make a copy of that branch in tags/ for each release candidate.
I just read up on the SVN docs at http://svnbook.red-bean.com/ and realized that there's no real difference between tags and branches - just a matter of naming and usage conventions, I guess. Good to see that SVN's adapted the Perforce notion of lazy branching (i.e copying). I guess this is a bit OT, but any ideas of when (and if) SVN will support the smart branching/integration/merging capabilities of Perforce? / Johan