-- Ralf Eggert <[email protected]> wrote (on Wednesday, 13 April 2011, 10:42 AM +0200): > > Our goal is a working version of the MVC by the end of May (if we can), > > a beta during the summer, and GA by end of year. Personally, I wouldn't > > start writing anything in earnest using the MVC until we get the working > > version ready. > > Good news, but just to clarify: will the GA release be the first final > release that could be used for production? Or will a production release > follow the GA?
GA == general availability, which is another way of saying stable. In other words, a GA release would be the first stable 2.0.0 version (vs. alpha or beta). > And what kind of changes could be implemented between the Beta and the > GA release? Just bug fixes or big changes breaking BC from GA to Beta? Beta is used to indicate general API stability, but not necessarily stable, production-ready code. As a general rule, you don't change interfaces between betas, but they _can_ be changed if usage bugs are found. Once we hit RC, the idea is bugfixes only, and really, at that point, only things that would affect general usability. -- 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]
