[os-infrastructure] Pragmatic Version Control using Subversion

[Stephen Ball]

Hmmmm...that was right last time I checked, wonder what happened.



Steve Ball
Direcor, Ingres DBMS Development
Ingres Corporation
stephen.ball at ingres.com

www.ingres.com 
 
This transmission is confidential and intended solely for the use of the recipient named above. It may contain confidential, proprietary, or legally privileged information. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this transmission in error, please contact the sender by reply e-mail and delete the original transmission and all copies from your system.


-----Original Message-----
From: opensource-infrastructure-bounces at lists.ingres.com [mailto:opensource-infrastructure-bounces at lists.ingres.com] On Behalf Of David Tondreau
Sent: Tuesday, May 13, 2008 10:26 AM
To: Discussions about the infrastructure needed to support a true open sourcecommunity
Subject: Re: [os-infrastructure] Pragmatic Version Control using Subversion

Dude, don't misspell your job title in your sig....

;-)


On 05/12/2008 08:21 PM, Stephen Ball wrote:
>
> Actually Subversion branching works much like piccolo branching, the 
> branches themselves are implemented as hard links on the server until 
> someone changes one of the files in the branch, at which time the link 
> is broken and replaced with a real file; so the disk implications of a 
> branch are very small...In any case disk is cheap.
>
> In piccolo taking a branch does normally take a few hours and numerous 
> branches eventually cause performance issues in the database, but the 
> time and performance problem in piccolo is largely a design issue, the 
> database itself was never designed with the intention of branching 
> numerous (over 8,000) files numerous times. We shouldn't assume that 
> in Subversion branching either takes a long time or causes database 
> performance issues, we need to test that aspect of it; since Grant has 
> taken a branch already he may be able to add some input.
>
> The one thing I'm worried about is the maintenance problem of numerous 
> branches; as far as I can see we can't avoid taking numerous branches 
> of the code in order to get the features we need (my read on the 
> documentation is the same as Alex's, we need to make a branch in order 
> to get a non head-rev tag), so how do we keep track of all the 
> branches and make sure the whole things doesn't become a big mess?
>
> If anyone is interested, I have managed to install a version of the 
> Subversive plug-in for Eclipse, and have it running against our 
> repository. If we are to get a grip on branch maintenance, a GUI tool 
> has to be in the picture, and Subversive looks promising. I have it 
> all rolled up into a VMWare VM running SuSE Linux if anyone wants a 
> copy; the VM includes SuSE 10.3, all the pre-requisites needed to 
> build Ingres pulled directly from the SuSE repository, a copy of 
> Eclipse with the CDT and the Subversive plug-in, and a complete 
> pre-built copy of Ingres from about a week ago.
>
> Steve
>
> IngresLogo_Color
>
> Steve Ball
>
> Direcor, Ingres DBMS Development
>
> *Ingres Corporation***
>
> stephen.ball at ingres.com <mailto:first.last at ingres.com>
>
> *www.ingres.com* <http://www.ingres.com>
>
> This transmission is confidential and intended solely for the use of 
> the recipient named above. It may contain confidential, proprietary, 
> or legally privileged information. If you are not the intended 
> recipient, you are hereby notified that any unauthorized review, use, 
> disclosure or distribution is strictly prohibited. If you have 
> received this transmission in error, please contact the sender by 
> reply e-mail and delete the original transmission and all copies from 
> your system.
>
> *From:* opensource-infrastructure-bounces at lists.ingres.com 
> [mailto:opensource-infrastructure-bounces at lists.ingres.com] *On Behalf 
> Of *Bodo Bergmann
> *Sent:* Tuesday, May 13, 2008 1:51 AM
> *To:* Alex Hanshaw; Discussions about the infrastructure needed to 
> support a trueopensource community; OpenSourceInfrastructure
> *Subject:* AW: [os-infrastructure] Pragmatic Version Control using 
> Subversion
>
> Yes, that's what I've already added to the Wiki page.
>
> But this implementation is both a waste of disk resources on the server
>
> and also has a huge performance impact as
>
> creating a label is not just a matter of seconds but will probably 
> take several minutes.
>
> Bodo.
>
> ------------------------------------------------------------------------
>
> *Von:* opensource-infrastructure-bounces at lists.ingres.com im Auftrag 
> von Alex Hanshaw
> *Gesendet:* Mo 12.05.2008 08:02
> *An:* OpenSourceInfrastructure
> *Betreff:* [os-infrastructure] Pragmatic Version Control using Subversion
>
> Hi all
>
> So far one of the problem areas we've mentioned with regards to 
> subversion is that there is no equivalent to a label.
> Some have already said "tags" do not provide the same functionality.
> However, in the above book I've just read "Tags can also be made from 
> a mixed revision working copy - a set of files you've checked out that 
> doesn't correspond to a single repository revision number". The book 
> only arrived today, I check out the rest of the tags and branches 
> section to see if this
> claim is true or not.
>
> Alex
>
>
>
> Alex Hanshaw
> Manager, Sustaining Engineering
>
> *Ingres Corporation*
>
> _Alex.Hanshaw at ingres.com <mailto:first.last at ingres.com>_
> *PHONE*+44 1753 559515
> *FAX*+44 1753 559550
>
> *_www.ingres.com <http://www.ingres.com/>_*
>
> This transmission is confidential and intended solely for the use of 
> the recipient named above. It may contain confidential, proprietary, 
> or legally privileged information. If you are not the intended 
> recipient, you are hereby notified that any unauthorized review, use, 
> disclosure or distribution is strictly prohibited. If you have 
> received this transmission in error, please contact the sender by 
> reply e-mail and delete the original transmission and all copies from 
> your system.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> opensource-infrastructure mailing list
> opensource-infrastructure at lists.ingres.com
> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
>   
_______________________________________________
opensource-infrastructure mailing list
opensource-infrastructure at lists.ingres.com
http://lists.ingres.com/mailman/listinfo/opensource-infrastructure