--- Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> Stefan Sperling <email@example.com> writes:
> > You don't have to mention "branches" or even "tags" to students
> > working with Subversion.
> > In fact these concepts can be explained easier than in CVS:
> > A tag is a copy of a directory that is (voluntarily) never
> > ever changed again.
> > A branch is a copy of a directory that is changed further
> > after the copy has been made.
> The fact that Subversion implements branch with "copy" doesn't mean
> that a branch _is_ a copy. There's no point having branches if you
> don't have merge, and there's very little point having it if you
> don't have switch.
There is the switch functionality - but it's just as easy to have a
second checkout. (if not easier)
> > But why do you even require your students to set a tag?
> As I said in my initial message, that allows them to continue working
> _and commititing_ close to the deadline. They can make a commit
> they're not 100% sure about, let other people review and test it, and
> then, after thinking twice, put a tag.
> > Or you could check out their project state at deadline time
> > by checking out by date (which would also work in CVS).
> This doesn't allow them to commit an "unofficial version" (i.e. a
> version for test, not taken into account by us until the tag).
> Well, we might go for this solution, but that would be a regression
> compared to what we used to do with the old CVS.
> At the moment, it seems the best solution is "delete; copy", but I
> don't like the window it lets without the tag present.
This is why I proposed the SVN layout that I did. You can go with a
more complicated layout like I presented, which gives you all the
functionality you described, or you can simplify and sacrifice some
functionality. It's your call. It's a matter of what you want to teach
them, and what they can handle. They'll have learn it eventually if
they're going to live in software, so they might as well get use to it
> > They could also tell you the revision number of their final
> > version (shown to them at every commit).
> That's a really primitive solution. That means we'd have to implement
> something to collect >60 version numbers (we have >200 students by
> group of 4). The revision control system is the tool with which I
> to manage revisions, I don't want another tool to simulate tagging.
See the archives for the discussions on this.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Oct 30 21:24:27 2007