On 9/24/07, Troy Bull <TBull@ifmc.org> wrote:
>
>
> >>> On 9/23/2007 at 6:21 PM, in message
> <ff892c5d0709231621j190dfac5w5dc98131372b12b0@mail.gmail.com>, "Mark Phippard"
> <markphip@gmail.com> wrote:
> > 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.
>
> So does this mean that the repository wont be FSFS after 1.5? Will 1.5 be able to
> read older repositories? (I have 1.3.2 FSFS repositories, that I was hoping to convert
> when 1.5 comes out).
Yes, there will be FSFS repositories in 1.5. They will hold a database
to store some metadata. Currently the database selected is SQLite, but
the rest of the repository will still store its data as it used to.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 24 15:04:27 2007