Version 1 by Matthew Weier O'Phinney
on May 22, 2008 13:43.

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (39)

View Page History
h3. Updating Your ZF SVN Checkout
<h3>Updating Your ZF SVN Checkout</h3>

<p>We just completed a reorganization of our subversion repository. The reorganization was necessary due to changes we are introducting both in our proposal system as well as project architecture. Specifically, we are introducing a new library, our 'Extras' library, which will contain contributions that are not officially supported by Zend but which still require successful completion of our proposal process. Additionally, we are merging our Laboratory repository.</p>

<p>The final structure is basically like the following:</p>

{code}
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
http://framework.zend.com/svn/framework/
standard/
laboratory/
build-tools/
{code}
]]></ac:plain-text-body></ac:macro>

The key changes:
<p>The key changes:</p>

<ul>
* tag/ <li>tag/ and branch/ have been moved under 'standard/' as 'tags/' and 'branches/', respectively</li>
* trunk/ has been moved to 'standard/trunk/'
* trunk/incubator/ has been moved to 'standard/incubator/'
* http://framework.zend.com/svn/laboratory has been moved to http://framework.zend.com/svn/framework/laboratory/
<li>trunk/ has been moved to 'standard/trunk/'</li>
<li>trunk/incubator/ has been moved to 'standard/incubator/'</li>
<li><a class="external-link" href="http://framework.zend.com/svn/laboratory">http://framework.zend.com/svn/laboratory</a> has been moved to <a class="external-link" href="http://framework.zend.com/svn/framework/laboratory/">http://framework.zend.com/svn/framework/laboratory/</a></li>
* trunk/build-tools/ <li>trunk/build-tools/ and trunk/scripts/ have been moved under build-tools/, and will contain their own branches and tags</li>
* addition of 'extras/' tree in repository
<li>addition of 'extras/' tree in repository</li>
</ul>

You will need to update your working checkouts and any svn:externals to point to the new locations.

If using subversion from the command line, switching your working checkout is relatively easy using 'svn info' and 'svn switch'. For example:
<p>You will need to update your working checkouts and any svn:externals to point to the new locations.</p>

<p>If using subversion from the command line, switching your working checkout is relatively easy using 'svn info' and 'svn switch'. For example:</p>
{code}
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
$ svn info .
Path: .

$ svn up
{code}
]]></ac:plain-text-body></ac:macro>

<p>To update your svn:externals checkouts, you will need to simply edit your svn:externals entries:</p>

{code}
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
$ svn propedit svn:externals .
{code}
]]></ac:plain-text-body></ac:macro>

<p>and simply edit the URL to which the externals point.</p>

<p>You will need to determine the final URL based on the information provided above about the changes. In general: </p>

<ul>
* if <li>if you were checking out from trunk, the path will change from 'trunk/' to 'standard/trunk/' 'standard/trunk/'</li>
* if <li>if you were checking out from a release branch, the path will change from 'branch/release-1.X/' to 'standard/branches/release-1.X/'</li>
* if <li>if you were checking out from a tag, the path will change from 'tag/release-1.X/' to 'standard/tags/release-1.X/'</li>
</ul>


<p>We apologize for any short term problems these changes may cause; however, they are necessary to allow us to expand our offerings and better support our community in the long term.</p>