Hi Bill!

Do you create a branch before or after the code freeze for new features for core components? Depending on the circumstances some of us could have new features ready before 1.0 is finished and it's complicated to manage that locally for ~1 month. Or should we copy the current state of our components to incubator (which would be equal to a new branch) in the meanwhile?

nico

[02.03.2007 03:48] Bill Karwin wrote:

Hi everyone,

Our schedule calls for a code-freeze on March 15, which is in two weeks
from today.  Let's talk a bit about the process for the Beta release.

The objective for the Beta release is that we are *feature complete*.
That means that any feature ideas for ZF components will have to wait
until after 1.0 to be included in the product.

We plan to have some number of Beta Refresh Releases, e.g. 0.9.1, 0.9.2,
etc., about once every two weeks.  These should include bug fixes and
improvements to documentation and tests, but no new features.

Any files that are still in incubator in ZF 0.9.0 will probably stay in
incubator until after 1.0.  We may make some exceptions in a Beta
Refresh, but they will be few and they will be evaluated carefully.

The incubator will be included in ZF 0.9.0, but not in subsequent
releases. After that release, files in the incubator will be accessible
only via subversion and nightly snapshots of svn.

When we feel the Beta Release and Beta Refresh Releases have served
their purpose and the product seems stable and complete, we will make a
1.0 Release Candidate.  We may make additional 1.0 Release Candidates,
about once every two weeks, until we feel it is ready to be called a 1.0
General Release.

So if we assume two Beta Releases and two 1.0 Release Candidates,
lasting two weeks each, that means we estimate the first 1.0 RC at
approximately April 12, and the final General Release at approximately
May 10.  If we can, we will make this date earlier.

We have seen a steady supply of good ideas coming in, and we regret that we cannot include all of them in Zend Framework 1.0. But there will be
opportunities after 1.0 to add more technology solutions.

Regards,
Bill Karwin

Reply via email to