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

Re: [TSVN] Some issues we are running into

From: <mjohnston_at_austar.com.au>
Date: 2005-09-12 01:11:33 CEST

I am sure you never understood correctly Nicke.

I think that Peter McNabs suggestions would fit my problem, and possible
solutions. Not a single piece of development was worthless, it just needed
to be rearranged due to project release schedules and the way we are being
forced to work by the business. Thanx for the attempted chastising email
anyway though.

Mark Johnston
IT Systems Development
Austar Communications Pty Ltd
w: http://www.austar.com.au
e: mjohnston@austar.com.au
p: 61 7 5560 6806
m: 61 417 726 718

                               | |
                               | |
                    Nicklas | To|
                    Norling | dev@tortoisesvn.tigris.org |
                    <exinor@exi| cc|
                    nor.net> | |
                    08/09/2005 | Subject|
                    10:47 PM | Re: [TSVN] Some issues we are |
                               | running into |
                            Ple| |
                            ase| |
                            res| |
                            pon| |
                             d | |
                            to | |
                            dev| |
                            @to| |
                            rto| |
                            ise| |
                            svn| |
                            .ti| |
                            gri| |
                            s.o| |
                            rg | |
                               | |
                               | |
                               | |
                               | |
  "AUSTAR celebrating 10 years | |
 in regional Australia" | |

mjohnston@austar.com.au wrote:

>We believe now that the best way to handle this would be to create a
>any time somebody starts a new project and let them do all their
>development on that branch. Then get them to merge back to the stable
>at time their project is ready for prime-time.
I think you're on to something :)

>The problem we are having directly atm is that we wish to branch off where
>our current trunk/head development is to a branch so that we don't lose
>code, but then we also wish to take one of the previous branch/head's and
>turn that into the mainline stable trunk/head that we can then further
>merge back into.
Uhh, this seems very confusing to me, are you really certain this is a
good move. I would recommend
trying to stick with keeping procedures as simple as possible to avoid
confusion which in it self can
cause problems. Trunk is just that, trunk, the finest most evolved
version of the software. Why do you
feel the need to suddenly abandon it for a branch?
I would stick with branches for features and then merge them to trunk,
or if things are uncertain, do all
dev on branches and make decisions on what should be on trunk and not.
Nothing is stopping you from
releasing certain stuff from a branch, you can merge other branches or
trunk into any feature branch if
that is needed.

>If I get a working copy down using tortoise (r41) we cannot then make that
>effectively become our trunk (> the previous trunk head of r100). When I
>then tried to commit that r41 to the head of the repository I got an error
>telling me that things were out of date and that I should do an update and
>I got an error of 106-1 or something to that effect.
So if I understand this right, your software is evolving from r41 to
r100 when you suddenly realize that
all the work in r41-r100 are pretty much worthless and should be
abandoned? This sounds very confusing
to me. Maybe more then the versioning system should be looked into here?
It's always possible to reverse
merge to get back to r41 and there are other methods as well but I'd
give my procedures a real good
thought before I did anything like that.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org

This message has been scanned for viruses by AUSTAR Communications
antivirus and content checking applications.
AUSTAR Communications

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Sep 12 01:12:04 2005

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