[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Source Control: Revisited

From: Noel Grandin <noel_at_peralex.com>
Date: 2005-02-28 06:49:42 CET

And frankly, having worked with a version control system that works at the method level (IBM VisualAge), I prefer simply
embedding the intelligence into the merging process - eclipse's CVS merge tools are a good example of this.

Embedding too much "intelligence" into the version control system results in an inflexible and fragile system.

Stellation is a good example of putting the intelligence into the wrong place - it undoubtedly represents a lot of work,
but you have to buy into a whole development style in order to use it.

Rather do one thing (version files) and do it well. This provides a well understood mental model for developers to work

Gerco Ballintijn wrote:
> Jani Averbach wrote:
>> On 2005-02-25 18:41+0100, Freek wrote:
>>> Hi,
>>> Code ist more than a simple textual representation of the things you
>>> want to do. How about going one point further and using a
>>> programming language aware(0) change detection in a source control
>>> system.
>> http://www.eclipse.org/stellation/
>> Motivation and Goals:
>> Fine granularity and Dynamic Program Organization. Stellation CM
>> will manage and version small artifacts, such as method
>> declarations, rather than entire source files. Fine granularity
>> makes it possible for programmers to coordinate their work with
>> greater precision, and to understand the impact of changes more
>> easily.
>> As in general I found this as an interesting idea, but there are more
>> important things to do, as locking (almost there!), merge tracking,
>> replication (at least read only slaves), new WC library, SQL backend,
>> etc.
> See also the following paper:
> @Article{MensT:2002may,
> author = "Tom Mens",
> title = "A State-of-the-Art Survey on Software Merging",
> journal = "IEEE Transactions on Software Engineering",
> volume = 28,
> number = 5,
> pages = "449--462",
> month = may,
> year = 2002
> }
> Gerco.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

NOTICE: Please note that this email, and the contents thereof,
are subject to the standard Peralex email disclaimer, which may
be found at: http://www.peralex.com/disclaimer.html

If you cannot access the disclaimer through the URL attached
 and you wish to receive a copy thereof please send
 an email to email@peralex.com

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 06:51:27 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.