Moving to the Apache SVN Server

[David E. Jones]

We've been mostly ready for the SVN server move for a while now, with license issues out of the way and such. We don't need all CLAs on file before moving to the new SVN server, we just need that before we can graduate from the incubator. That is getting pretty close to done, as are many other things, so we are actually pretty close to graduation.

For the SVN move we'll use something like the following process. Because of this we'll want to do it during a slower time, so I'm planning on working on this on Saturday. Things are usually pretty slow starting around mid-day Friday, but Saturday is probably better. Here are the steps:

1. shut off all commit access to the old SVN server (http://svn.ofbiz.org/svn/ofbiz/trunk)

2. do a fresh checkout from the old server and import the relevant parts of the repository to the new server (which will be at: http://svn.apache.org/repos/asf/incubator/ofbiz/trunk)

3. remove the parts added to the new SVN server from the old SVN server (only specialized and such will remain); this will happen a few days after the original repository is removed to avoid problems with people accidentally doing an "svn up" against the old server; we'll warn against this but I GUARANTEE we'll get complaints because people will do this and watch their local checkout (except for modified/added files) get cleaned out; this isn't a huge problem as you can always start with a new checkout, but copying files over files that have changed may result in cutting out changes in the repository; I'll try to warn about this and perhaps I'm being pessimistic, but I'm sure people will do it and cause themselves problems, and possibly cause problems with patches submitted for up to a few weeks after this switch

4. restore commit access as needed for the old server; commit access can be used immediately on the new server

Please note that after this move you'll need to start checking out from the new server. Because not all of the old SVN repository will be moved to the new server changing the location will have to be done on just the moved resources. It can be done without re-checking out using the "svn switch" command, something like the following (for example only) from the ofbiz home directory:

$ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/

If anyone has any thoughts or commentary on this, let me know.

-David

[David E. Jones]

David E. Jones wrote:
> Please note that after this move you'll need to start checking out from
> the new server. Because not all of the old SVN repository will be moved
> to the new server changing the location will have to be done on just the
> moved resources. It can be done without re-checking out using the "svn
> switch" command, something like the following (for example only) from
> the ofbiz home directory:
>
> $ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/

This was wrong, missing the "trunk"... should be:

$ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/trunk framework/

-David

[Andrew Sykes]

Is it necessary to remove stuff from the old server on a strict
timescale?

Wouldn't it solve a few of these issues of that old version was just
left to languish for a while?

- Andrew

On Thu, 2006-06-29 at 11:01 -0600, David E. Jones wrote:

> We've been mostly ready for the SVN server move for a while now, with license issues out of the way and such. We don't need all CLAs on file before moving to the new SVN server, we just need that before we can graduate from the incubator. That is getting pretty close to done, as are many other things, so we are actually pretty close to graduation.
>
> For the SVN move we'll use something like the following process. Because of this we'll want to do it during a slower time, so I'm planning on working on this on Saturday. Things are usually pretty slow starting around mid-day Friday, but Saturday is probably better. Here are the steps:
>
> 1. shut off all commit access to the old SVN server (http://svn.ofbiz.org/svn/ofbiz/trunk)
>
> 2. do a fresh checkout from the old server and import the relevant parts of the repository to the new server (which will be at: http://svn.apache.org/repos/asf/incubator/ofbiz/trunk)
>
> 3. remove the parts added to the new SVN server from the old SVN server (only specialized and such will remain); this will happen a few days after the original repository is removed to avoid problems with people accidentally doing an "svn up" against the old server; we'll warn against this but I GUARANTEE we'll get complaints because people will do this and watch their local checkout (except for modified/added files) get cleaned out; this isn't a huge problem as you can always start with a new checkout, but copying files over files that have changed may result in cutting out changes in the repository; I'll try to warn about this and perhaps I'm being pessimistic, but I'm sure people will do it and cause themselves problems, and possibly cause problems with patches submitted for up to a few weeks after this switch
>
> 4. restore commit access as needed for the old server; commit access can be used immediately on the new server
>
> Please note that after this move you'll need to start checking out from the new server. Because not all of the old SVN repository will be moved to the new server changing the location will have to be done on just the moved resources. It can be done without re-checking out using the "svn switch" command, something like the following (for example only) from the ofbiz home directory:
>
> $ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/
>
> If anyone has any thoughts or commentary on this, let me know.
>
> -David
>

--
Kind Regards
Andrew Sykes <[hidden email]>
Sykes Development Ltd
http://www.sykesdevelopment.com

[Jacopo Cappellato]

David,

that's great news.
I'd suggest to post this message to the user list as well since many of
the OFBiz users are running the svn trunk.

Jacopo

David E. Jones wrote:

>
> We've been mostly ready for the SVN server move for a while now, with
> license issues out of the way and such. We don't need all CLAs on file
> before moving to the new SVN server, we just need that before we can
> graduate from the incubator. That is getting pretty close to done, as
> are many other things, so we are actually pretty close to graduation.
>
> For the SVN move we'll use something like the following process. Because
> of this we'll want to do it during a slower time, so I'm planning on
> working on this on Saturday. Things are usually pretty slow starting
> around mid-day Friday, but Saturday is probably better. Here are the steps:
>
> 1. shut off all commit access to the old SVN server
> (http://svn.ofbiz.org/svn/ofbiz/trunk)
>
> 2. do a fresh checkout from the old server and import the relevant parts
> of the repository to the new server (which will be at:
> http://svn.apache.org/repos/asf/incubator/ofbiz/trunk)
>
> 3. remove the parts added to the new SVN server from the old SVN server
> (only specialized and such will remain); this will happen a few days
> after the original repository is removed to avoid problems with people
> accidentally doing an "svn up" against the old server; we'll warn
> against this but I GUARANTEE we'll get complaints because people will do
> this and watch their local checkout (except for modified/added files)
> get cleaned out; this isn't a huge problem as you can always start with
> a new checkout, but copying files over files that have changed may
> result in cutting out changes in the repository; I'll try to warn about
> this and perhaps I'm being pessimistic, but I'm sure people will do it
> and cause themselves problems, and possibly cause problems with patches
> submitted for up to a few weeks after this switch
>
> 4. restore commit access as needed for the old server; commit access can
> be used immediately on the new server
>
> Please note that after this move you'll need to start checking out from
> the new server. Because not all of the old SVN repository will be moved
> to the new server changing the location will have to be done on just the
> moved resources. It can be done without re-checking out using the "svn
> switch" command, something like the following (for example only) from
> the ofbiz home directory:
>
> $ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/
>
> If anyone has any thoughts or commentary on this, let me know.
>
> -David
>
>

[Yoav Shapira-2]

Howdy,
Just out of personal curiosity:

On 6/29/06, Jacopo Cappellato <[hidden email]> wrote:
> I'd suggest to post this message to the user list as well since many of
> the OFBiz users are running the svn trunk.

Does OFBiz actually track this somehow?  Do we know how many "many"
is?  I don't mind any way or any answer value, as I said just
personally curious.

Yoav

[Ray Barlow]

Considering this is quite a major change and refactor of the source
structures in terms of how and where to get everything and use it,
should this be done as a branch on the old SVN server?

Forgive me if I've missed it, although I can guess at most of it, it
might be a good idea to throw together a page outlining the new
structure and how the new and old server will be related. More so for
areas that require the old server i.e. cybersource, pos drivers, jasper,
shark and worldpay etc rather than the actual specialised additional
projects. Thinking about it maybe refactoring the specialised folder
would also be in order as it now contains more than just non-core
specialised projects?

Ray

David E. Jones wrote:

>
> We've been mostly ready for the SVN server move for a while now, with
> license issues out of the way and such. We don't need all CLAs on file
> before moving to the new SVN server, we just need that before we can
> graduate from the incubator. That is getting pretty close to done, as
> are many other things, so we are actually pretty close to graduation.
>
> For the SVN move we'll use something like the following process.
> Because of this we'll want to do it during a slower time, so I'm
> planning on working on this on Saturday. Things are usually pretty
> slow starting around mid-day Friday, but Saturday is probably better.
> Here are the steps:
>
> 1. shut off all commit access to the old SVN server
> (http://svn.ofbiz.org/svn/ofbiz/trunk)
>
> 2. do a fresh checkout from the old server and import the relevant
> parts of the repository to the new server (which will be at:
> http://svn.apache.org/repos/asf/incubator/ofbiz/trunk)
>
> 3. remove the parts added to the new SVN server from the old SVN
> server (only specialized and such will remain); this will happen a few
> days after the original repository is removed to avoid problems with
> people accidentally doing an "svn up" against the old server; we'll
> warn against this but I GUARANTEE we'll get complaints because people
> will do this and watch their local checkout (except for modified/added
> files) get cleaned out; this isn't a huge problem as you can always
> start with a new checkout, but copying files over files that have
> changed may result in cutting out changes in the repository; I'll try
> to warn about this and perhaps I'm being pessimistic, but I'm sure
> people will do it and cause themselves problems, and possibly cause
> problems with patches submitted for up to a few weeks after this switch
>
> 4. restore commit access as needed for the old server; commit access
> can be used immediately on the new server
>
> Please note that after this move you'll need to start checking out
> from the new server. Because not all of the old SVN repository will be
> moved to the new server changing the location will have to be done on
> just the moved resources. It can be done without re-checking out using
> the "svn switch" command, something like the following (for example
> only) from the ofbiz home directory:
>
> $ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/
>
> If anyone has any thoughts or commentary on this, let me know.
>
> -David
>
>

[davidnwelton]

Offhand suggestion, as the final checkin to the old repository, after
the switch, a file along the lines of

USE_THE_NEW_REPOSITORY

containing the command line needed to switch to the new repository.

--
David N. Welton
 - http://www.dedasys.com/davidw/

Linux, Open Source Consulting
 - http://www.dedasys.com/

[David E. Jones]

There will be no structure change moving to the new repository. It will be an exact import of an export from the old one. Or, perhaps I'm misunderstanding what you mean by that?

-David


Ray Barlow wrote:

> Considering this is quite a major change and refactor of the source
> structures in terms of how and where to get everything and use it,
> should this be done as a branch on the old SVN server?
>
> Forgive me if I've missed it, although I can guess at most of it, it
> might be a good idea to throw together a page outlining the new
> structure and how the new and old server will be related. More so for
> areas that require the old server i.e. cybersource, pos drivers, jasper,
> shark and worldpay etc rather than the actual specialised additional
> projects. Thinking about it maybe refactoring the specialised folder
> would also be in order as it now contains more than just non-core
> specialised projects?
>
> Ray
>
> David E. Jones wrote:
>>
>> We've been mostly ready for the SVN server move for a while now, with
>> license issues out of the way and such. We don't need all CLAs on file
>> before moving to the new SVN server, we just need that before we can
>> graduate from the incubator. That is getting pretty close to done, as
>> are many other things, so we are actually pretty close to graduation.
>>
>> For the SVN move we'll use something like the following process.
>> Because of this we'll want to do it during a slower time, so I'm
>> planning on working on this on Saturday. Things are usually pretty
>> slow starting around mid-day Friday, but Saturday is probably better.
>> Here are the steps:
>>
>> 1. shut off all commit access to the old SVN server
>> (http://svn.ofbiz.org/svn/ofbiz/trunk)
>>
>> 2. do a fresh checkout from the old server and import the relevant
>> parts of the repository to the new server (which will be at:
>> http://svn.apache.org/repos/asf/incubator/ofbiz/trunk)
>>
>> 3. remove the parts added to the new SVN server from the old SVN
>> server (only specialized and such will remain); this will happen a few
>> days after the original repository is removed to avoid problems with
>> people accidentally doing an "svn up" against the old server; we'll
>> warn against this but I GUARANTEE we'll get complaints because people
>> will do this and watch their local checkout (except for modified/added
>> files) get cleaned out; this isn't a huge problem as you can always
>> start with a new checkout, but copying files over files that have
>> changed may result in cutting out changes in the repository; I'll try
>> to warn about this and perhaps I'm being pessimistic, but I'm sure
>> people will do it and cause themselves problems, and possibly cause
>> problems with patches submitted for up to a few weeks after this switch
>>
>> 4. restore commit access as needed for the old server; commit access
>> can be used immediately on the new server
>>
>> Please note that after this move you'll need to start checking out
>> from the new server. Because not all of the old SVN repository will be
>> moved to the new server changing the location will have to be done on
>> just the moved resources. It can be done without re-checking out using
>> the "svn switch" command, something like the following (for example
>> only) from the ofbiz home directory:
>>
>> $ svn switch http://svn.apache.org/repos/asf/incubator/ofbiz/ framework/
>>
>> If anyone has any thoughts or commentary on this, let me know.
>>
>> -David
>>
>>