Hi Adam, If you are already using SVN to manage your application source code, you might also consider the use of svn:externals:
http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html You can set the revision to which the externals definition applies, helping you to easily manage framework upgrades between releases if desirable. Externals defintions are also most convenient for bleeding edge development, where an svn update in your application working copy also updates your framework copy to the latest SVN revision. If you are not using SVN for your application sources, you can also use svn export, which operates upon a particular revision if supplied. Where a subversion client is unavailable, you may of course download the releases or nightly snapshots from the website. Best regards, Darby Adam Balgach wrote: > Greetings all, > > i am trying to write Zend into our deployment scripts for both > production and development, and just wanted to be sure that I am using > the correct subversion repositories for them [this is mainly a doublecheck] > > Releases (where current R.X.x is 0.8.0) > > http://framework.zend.com/svn/framework/tag/release-R.X.x > > (so in the future v.1.0.0 will eventually be > http://framework.zend.com/svn/framework/tag/release-1.0.0) > > and development nightly build: > > http://framework.zend.com/svn/framework/trunk/ > > > Is there any road map to change these locations? I assume not, but just > want to be 100%. > > Cheers, > A. > >
