View Source


<p>Zend Framework releases will be identified in the form <strong>x.y.z</strong>, where:</p>

<p>1) Any increment of <strong>x</strong> denotes a <strong>major release</strong><br />
2) Any increment of <strong>y</strong> denotes a <strong>minor release</strong><br />
3) Any increment of <strong>z</strong> denotes a <strong>mini release</strong></p>

<p>Each release may contain the following:</p>

<p>1) A <strong>major release</strong> may contain any changes, including <strong>bug fixes</strong>, <strong>backwards compatible features and functionality enhancements</strong>, and <strong>backwards incompatible releases</strong>.<br />
2) A <strong>minor release</strong> may only contain backwards compatible changes, including <strong>bug fixes</strong> and <strong>backwards compatible features and functionality enhancements</strong>.<br />
3) A <strong>mini release</strong> may only contain <strong>bug fixes</strong>. <strong>Note that no new features, functionality enhancements, or API changes are allowed whatsoever.</strong> The framework should look and behave the same across mini releases.</p>

<p>No attempt will be made to make Zend Framework releases forwards compatible.</p>

<p>New features are defined as changes that offer new or significantly enhanced API's. These features typically require <ac:link><ri:page ri:content-title="home" ri:space-key="ZFPROP" /><ac:link-body>proposals</ac:link-body></ac:link>.</p>

<p>Functionality enhancements are defined as behavioral changes that do not affect- or minimally affect- one or more API's. Such functionality enhancements typically do not require a <ac:link><ri:page ri:content-title="home" ri:space-key="ZFPROP" /><ac:link-body>proposal</ac:link-body></ac:link></p>

<p>Exceptions to these policies will only be permitted for security fixes.</p>


<p>We try to build <strong>mini releases</strong> on a bi-weekly schedule. For example, the current release is 1.7.7. It was released on 3/6/2009. The next release will be called 1.7.8 and will be released on 3/23/2009.</p>

<p>We try to build <strong>minor releases</strong> once every quarter. That is, each release will be available 3-month after the last release as a rule of thumb. This convention is flexible; for larger releases we may require up to 6 months of development time.</p>

<p>We do not target any periodic schedule for <strong>major releases</strong>, as backwards compatibility will be broken only when the value-add for ZF users has become very high. Schedules for <strong>major releases</strong> can span well over a year.</p>

<p>These are only conventions; they will be updated or broken as necessary.</p>