Binzy Wu wrote:
I think it's ok to upgrade, if you haven't implemented your own Front, Dispatcher or Router. But I am confused with the interface change. Why don't leave the old methods? Just since these are preview versions? But it's ok. They are still in incubator...
Exactly. This is one reason for the convention that component interface changes are released in the incubator first, and then migrate to the core library only after at least one release. This allows everyone with existing code to test and adapt to the new interfaces. I intend that the changes to MVC move to the core library soon, but it would be too disruptive to make those changes without first letting them appear in the incubator.
Keep in mind that Zend Framework is still in "Preview Release". This state is pre-"Beta" which means that interfaces are not contracts. Interfaces may change as the components are improved, as we move toward a final Production release 1.0. After the Production release, APIs are stable and we must do everything we can not to break backward compatibility.
Regarding component-level changelogs, right now we have a automated changelog that JIRA supplies. I have marked version 0.2.0 as "released" so now anything that was recorded in JIRA and marked as fixed in 0.2.0 the list shows up in the changelog view. See http://framework.zend.com/issues/browse/ZF?report=com.atlassian.jira.plugin.system.project:changelog-panel
The automatically generated change log has the disadvantage that anything _not_ represented in JIRA doesn't get listed. To understand the full changes, we have to read Developer Notes (http://framework.zend.com/wiki/x/sg) and Proposals (http://framework.zend.com/wiki/x/Lw). I like the idea of writing more detailed changelogs. That will be easier if we make releases more frequently.
Regards, Bill Karwin
