RE: 1.5 beta stability

Would a simple svnadmin dump and load between upgrades be enough to deal
with this?

We only have 21,000 or so commits so it's no huge task to run it overnight
if I want to upgrade.

-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Monday, 24 September 2007 9:22 AM
To: Greg Irvine
Cc: users@subversion.tigris.org
Subject: Re: 1.5 beta stability

On 9/23/07, Greg Irvine <greg.irvine@thalesatm.com> wrote:
> My project is about to branch from our product branch for a new client
> program. We will be merging critical fixes to the program branch for
things
> fixed in the product branch as well as some product evolutions the program
> will be interested in.
>
> Obviously 1.5's merge tracking will make our lives far easier.
>
> So, is the current unreleased 1.5 code stable enough for us to use in a
> production environment (with the usual disclaimer that it's still a beta
and
> risk is all mine)?

Yes, I think it is. The one thing to be aware of is that it is
possible the repository will change and there would not be any attempt
to maintain compatibility with prior trunk versions. For example, the
repository now uses a SQLite database. Someone could decide to add a
new field or index (there has been talk of renaming the file). You
would have to manually deal with this if it happened.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org