-- Andrei Iarus <[email protected]> wrote
(on Friday, 18 March 2011, 08:32 AM -0700):
> probably the best way to keep Zend Framework up-to-date in a project
> is using svn:externals. But The questions are:
>
> 1. Which URL and which version should one use?
> 2. How sure is that a stable version didn't change its behaviour?
I typically recommend pinning to a branch during development, and a tag
during production.
Branches are located at:
http://framework.zend.com/svn/framework/standard/branches/
and prefixed with "release-" and named after the minor release version:
"release-1.11", etc.
Tags are located at:
http://framework.zend.com/svn/framework/standard/tags/
and prefixed with "release-" and named after the release version:
"release-1.11.4", etc.
Version 1.X is considered stable; typically, you will want to run code
from the most recent minor release branch, currently 1.11.
Versions are named <major>.<minor>.<maintenance>. "1.11.4" means "major
version 1, minor version 11, maintenance release 4". Within a major
version, we aim to maintain backwards compatibility; exceptions to this
occur when the only fix to a long-standing issue means breaking the API
(e.g., this occurred with Zend_View between 1.7 and 1.8, when we
discovered an encoding issue that could lead to security issues).
We encourage rigorous testing of your applications whenever you update
your ZF installation to ensure no breakages occur.
--
Matthew Weier O'Phinney
Project Lead | [email protected]
Zend Framework | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
