[greenstone-devel] Re: [greenstone-users] Greenstone tag names

From mdewsnip@cs.waikato.ac.nz
DateTue, 20 Nov 2007 10:17:17 +1300 (NZDT)
Subject [greenstone-devel] Re: [greenstone-users] Greenstone tag names
In-Reply-To (4740A3BA-7080600-cs-waikato-ac-nz)
Hi Oran,

I'm strongly in favour of "If it ain't broke...".

I expect there are very few users who actually get Greenstone from SVN,
and I think we probably make up a lot of those that do. We need old
versions of Greenstone all the time, and we'd need to change the
documentation for all our projects if the tag names changed.

Also, I don't think the existing tag names are "horrible" -- they may be
verbose, but I never think that's a bad thing. And they've worked just
fine for the last 7 years.

Regards,

Michael

--
DL Consulting
Greenstone Digital Library and Digitisation Specialists
contact@dlconsulting.com
www.dlconsulting.com

> The current names of tags in our repository are horrible and
> CVS-oriented. How would people feel if we renamed all the old tags to
> fit a new naming convention (/<project>/branches/<x.xx> and
> /<project>/tags/<x.xx>? With SVN you get all the info you need from the
> repository path, so there is no need to duplicate it in the tag name;
> gsdl/tags/2.75 looks better in the repository than
> gsdl/tags/gsdl-2_75-distribution, and is much easier to remember when
> you type it on the command line or in code. And if the name of
> working-copys are a concern, SVN allows you to call a working-copy
> anything you want, with the syntax 'svn co <url> working-copy-name'.
> This would be made clear in our wiki documentation.
>
> Cheers,
> Oran.
>
>
> Michael Dewsnip wrote:
>> Don't worry, I've done it myself (and "indexers" too).
>>
>> Cheers,
>>
>> Michael
>>
>>
>>
>> Michael Dewsnip wrote:
>>> Hi Oran,
>>>
>>> Thanks. It is possible to tag the 2.75 release with "" as well, to be
>>> consistent with the other releases?
>>>
>>> Cheers,
>>>
>>> Michael
>>>
>>>
>>>
>>> Oran Fry wrote:
>>>> I have tagged the 2.75 release and the 3.03 release in the
>>>> repository. In other words, I have moved /*/branches/2.75 to
>>>> /*/tags/2.75 and /*/branches/3.03 to /*/tags/3.03. The commit
>>>> messages all say 'tagging the 2.75 release'. Sorry about that, my
>>>> mistake.
>>>>
>>>> Cheers,
>>>> Oran.
>>>>
>>>> Michael Dewsnip wrote:
>>>>> Hi Oran,
>>>>>
>>>>> Sounds good... will you be tagging the reposit