-- Colin Guthrie <[email protected]> wrote (on Wednesday, 11 February 2009, 11:15 PM +0000): > 'Twas brillig, and Benjamin Eberlei at 11/02/09 17:03 did gyre and gimble: > > you should create an account at http://framework.zend.com/issues and file > > issues against Zend_Db, put their alert level up based on what you think is > > necessary. Also make sure not to put all the things into one issue, but > > split them up so that they are unique items to be worked at. > > ... and supply patches ;)
That last statement cannot be emphasized nearly enough. Most issues that suggest changes merely for the sake of OO purity will be ignored in favor of _real_ issues/feature requests. There's simply very little, if any, benefit to investing the time to make the changes in most cases. However, if you supply a _patch_ -- especially if it contains unit tests for any functional changes -- we'll be much more likely to apply them and accept the change. -- Matthew Weier O'Phinney Software Architect | [email protected] Zend Framework | http://framework.zend.com/
