Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Zend Framework Subversion Standards

What is Subversion?

"SVN (Subversion) is a tool used by many software developers to manage changes within their source code tree. SVN provides the means to store not only the current version of a piece of source code, but a record of all changes (and who made those changes) that have occurred to that source code. Use of SVN is particularly common on projects with multiple developers, since SVN ensures changes made by one developer are not accidentally removed when another developer posts their changes to the source tree."

The Zend Framework Subversion Repository

The Zend Framework is an open source project and the complete source code can be downloaded anonymously by direct checkout from its Subversion repository. For information on how to receive automatic notification of changes and updates to the Zend Framework and documentation, please see [Zend Framework RSS Feeds and Notifications].

Anonymous Checkout

The most up-to-date working copy of the Zend Framework is the trunk. This includes all the newest features and bugfixes and incubator components. However, the latest versions of each file often have far less testing and possibly more bugs than the versions found in the most recently released, stable version of the Zend Framework in the Download area.

SVN Checkout

Please report new bugs, submit patches, or comment on posted issues using the Issue Tracker on the Developer's Wiki.

Prior Release Versions

All versions of the Zend Framework that are released to the public are tagged and also available for download from the repository. Checkout or export and check the tags directory for previous releases.

Subversion Write / Commit Access

Access SVN is granted to component area leads and higher volume contributors. If you need access to SVN you may request it on the mailing list or through a component lead that you have worked with previously.

A few rules should be kept in mind when using SVN:

  • All commits should contain commit comments.
  • If a commit is resolving an issue from the issue tracker, the issue KEY should be indicated in the commit comment (i.e. "This resolves ZF-2"). This will cause it to be auto-linked from Fisheye to the issue, and also the reverse link from the issue back to Fisheye. The issue key can be seen when viewing any issue in the upper left corner of the screen.
  • All commits that would affect release notes should have an associated issue in the tracker. There are issue types for most situations, and if it is just a significant change that does not fit into another category, use the issue type "Patch."
  • It is no longer neccessary to update NEWS.TXT as the issue tracker will be used to generate release notes.
  • When resolving an issue, feel free to edit the issue's title to be clearer based on anything you learned while fixing it. This will aid the readability of the release notes.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.