Yes, I understand and agree that the best fix for a bug is sometimes to implement a new feature.
But if the new features aren't implemented by the code-freeze on March 15, they must wait until after 1.0. That means the bug will not be fixed in 1.0. The date is a deadline. We can't do everything in a finite amount of time. We just have to accept that some things won't be added until the next release. We must release ZF 1.0, we can't continue to develop it without releasing. Of course rules can always have exceptions, so if there is a case you want to be considered as an exception, please bring it up to myself and Andi Gutmans. We will be the arbiters of change control during the Beta period. Regards, Bill Karwin > -----Original Message----- > From: Thomas Weidner [mailto:[EMAIL PROTECTED] > Sent: Friday, March 02, 2007 12:24 AM > To: Bill Karwin; [email protected] > Subject: Re: [fw-general] Zend Framework 0.9 code freeze schedule > > Hy Bill, > > >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. > > What does this mean for already proposed issues within Jira ? > Is it able to include them or not ? > > Some of the problems can only be solved by changing the API or > implementing > new features and erasing old behaviour. > > In generally I am speaking of the actual I18N issues, but it is also > relevant for all other classes. > > Greetings > Thomas > I18N Team Leader
