[Biococoa-dev] Re: Subversion proposal
Peter Schols
peter.schols at bio.kuleuven.be
Mon Mar 6 17:06:01 EST 2006
Hi Charles,
I follow your explanation and I agree with the philosophy of having
stable tags and a trunk which is work in progress. I see two problems
though:
- I always see tags as a snapshot of the trunk at a certain point in
time. With this structure, we'd end up with a tag that has code which
is not represented in the trunk (the code Alex has submitted). So it
wouldn't be a snapshot at all. In itself, this might not be a major
problem, it just seems very confusing to me (but that might be just
my short-sighted view of version control ;-)).
- The point of including Alex's code into the repository is to be
able to easily work on it and improve it. If we'd make it a tag, we
are no longer 'allowed' to modify it (unless we make new tags for
every little change), defeating the purpose of putting it under
version control (except for the fact that all code is contained in
one download). With this approach, we could as well offer Alex's code
as a download without checking it in. In both cases, the code would
be virtually 'unchangeable' until we check it into the main trunk.
Again, I'm definitely not a specialist and I think we could either
include or exclude Alex's code from the repository, either choice is
OK with me. The point I would like to make here is that if we include
it, it should also be in the trunk (and we can then make a tag for
the 1.7 release). Apologies if I'm missing something here.
peter
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
More information about the Biococoa-dev
mailing list