[GenABEL-dev] Adding 'tags' directories to the SVN repo

[Yurii Aulchenko]

Just had discussed this in person with Lennart.

Probably the most straightforward solution is to add 'tags' directory
at the same level where 'pkg' and 'www' are. Inside, we will have
directories like

GenABEL
ProbABEL
MetABEL
...
etc.

Within these, we can put our tags, named after version.

If someone sees a better solution, please reply, otherwise we will
proceed with this idea (I plan to submit GenABEL 1.6-7 within next few
days, as it addresses one important bug fix).

Yurii

On Tue, May 17, 2011 at 9:33 AM, Yurii Aulchenko
<yurii.aulchenko at gmail.com> wrote:
> Having tags is a good idea indeed.
>
> Something to keep in mind: RForge is doing nightly builds under
> different platforms, assuming that any directory under 'pkg' is a
> regular package source. This is a tool of potentially great value.
> Maybe RForge docs and consulting RForge team on how to best arrange
> tags is a good idea.
>
> Bw,
> Yurii
>
>
> On 5/16/11, L.C. Karssen <l.karssen at erasmusmc.nl> wrote:
>> Dear all,
>>
>> In the past there were several discussions, both on-line and off-line,
>> on the layout of the Subversion repository.
>>
>> After releasing ProbABEL 0.1-9e yesterday and with the upcoming release
>> of GenABEL 1.6.7 I think it is time to implement one of these structural
>> changes: the addition of a 'tags' subdirectory.
>>
>> Such a tags directory is used to create snapshots of the development
>> tree at a certein time, for example at each release of a package. This
>> way it is easier to get an overview of the previous releases without
>> having to dig through the SVN logs. The idea is of course that the files
>> in such directory should be treated as read only (otherwise they become
>> a branch, but that's for some other time).
>>
>> There are two basic designs for a repository layout with tags (based on
>> our present layout) [1]:
>> /
>>    www/
>>    pkg/
>>       GenABEL/
>>          trunk/
>>          tags/
>>             v1.6.6/
>>             v1.6.7/
>>       ProbABEL/
>>          trunk/
>>          tags/
>>             v0.1-9d/
>>             v0.1-9e/
>> In this scenario each sub-project has its own trunk (for normal
>> development) and tags directory.
>>
>> The second design is:
>> /
>>    www/
>>    pkg/
>>       GenABEL/
>>       ProbABEL/
>>    tags/
>>       GenABEL/
>>          v1.6.6/
>>          v1.6.7/
>>       ProbABEL/
>>          v0.1-9d/
>>          v0.1-9e/
>> This design is most easy to implement in our case since it does not
>> change anything to the structure of the sub-projects. We simply create a
>> tags directory under / and put the tags there. It is, however, slightly
>> counterintuitive because most repositories follow the first design and a
>> checkout of /pkg/GenABEL in design 2 will not include the tags, only the
>> trunk. For our present contributors design 2 means no real change (no
>> changing of URLs for checkouts, no extra subdirectory (trunk) to change
>> into, etc.).
>>
>> In short, I suggest going for the second design. It is easy to implement
>> and does not change anything for contributors. Of course we can always
>> decide to move to design 1 at a later stage when we also allow for
>> branches.
>>
>> What are your ideas? One of these layouts, an entirely different one?
>>
>>
>> Regards,
>>
>> Lennart.
>>
>> [1] The Subversion book,
>> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html
>> --
>> -----------------------------------------------
>> L.C. Karssen
>> Erasmus MC
>> Department of Epidemiology
>> Room 2224
>>
>> Postbus 2040
>> 3000 CA Rotterdam
>> The Netherlands
>>
>> phone: +31-10-7044217
>> fax: +31-10-7044657
>> e-mail: l.karssen at erasmusmc.nl
>> GPG key ID: 0E1D39E3
>> -----------------------------------------------
>>
>
> --
> Sent from my mobile device
>