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

Re: Final(?) format bump for 1.7: Format 29

From: Julian Foad <julian.foad_at_wandisco.com>
Date: Tue, 31 May 2011 10:29:53 +0100

Thanks for removing the code that I had put in to introduce validation
triggers into the DB. I intended to remove that but hadn't yet done so.

Monday was a public holiday in the UK and USA so I've only just seen
your email announding this format bump.

- Julian

On Sun, 2011-05-29 at 15:56 +0200, Bert Huijben wrote:
> Hi,
> I intend to bump the working copy format to format 29 tomorrow Monday May
> 29, in the late afternoon/early evening (CEST).
> This format bump will rename all the pristines files from earlier WC-NG
> formats to have the extension .svn-base and it will add the EXTERNALS table.
> The externals table is a new table which will keep track of what externals
> are currently described by the working copy. It allows processing local
> svn:externals properties in a guaranteed way and provides our API with the
> knowledge on which node a svn:external is defined.
> I hope you don't notice anything from the format bump as this will be
> handled as an automatic conversion like most other intermediate format
> bumps. But if you do encounter problems, please let us know.
> Unrelated to this format bump, but:
> Over the next weeks (Most likely *after* the June 1 milestone) we intend to
> define a last revision that supports upgrading from all the intermediate 1.7
> releases (formats 12 to 28) to the final 1.7 format. At that point we will
> remove the temporary upgrade code from these intermediate formats.
> Of course we won't remove the upgrade code from 1.6.x (<= format 10) and
> earlier entries as that upgrade will be supported for all future 1.X
> releases.
> Bert
Received on 2011-05-31 11:30:32 CEST

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.