Re: Addition to documentation on branch/tag? (Or did I miss it in my search:)

Kevin Greiner wrote:
> On 2/3/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
>> On 2/3/06, si <sshnug.si@gmail.com> wrote:
>>
>>> I think I can understand the rational (because the location already
>>> exists and a copy shouldn't overwrite data), but it was tricky to figure
>>> out the reason, because the directory was empty to begin with.
>> http://subversion.tigris.org/issues/show_bug.cgi?id=2188
>
> It appears this issue was resolved a few days ago. But as TSVN is
> currently built against the svn 1.3.0 tag, this API change won't be
> available until TSVN is built against a new (not yet existing) svn
> tag, right? What is the policy for switching to build against a new
> svn tag?
>
> I was sure I remembered seeing this discussion before but couldn't
> find it in the archives or website.

That policy is simple: we switch as soon as a new tag is created in the
Subversion repository. But not before.
Of course, sometimes we switch to a branch or even the Subversion trunk,
but only on our own trunk, not the release branch or even for a release.

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