Stalled custom field development

Stuart Donaldson stu at asyn.com
Fri Apr 1 14:54:10 UTC 2005


>>Actually, it is not paralyzed at all unless someone is foolish enough 
>>to try to do the whole thing in one huge patch that will never land.
>>    
>>
>When somebody has an existing working implementation it doesn't seem 
>at all foolish to wish that it could land. 
>  
>
<soapbox>
Here is a bit of an oversimplified view, but too much stagnation often 
calls for drastic action.

Ya know if the proposal from Sean had landed several months back when he 
proposed it, you would have many many happy users of Bugzilla out there 
with a working custom fields implementation.  Then even if you found the 
schema to be needing change, you could put all the work that is now 
being called for into Fielddefs and then change the schema later.  The 
biggest downside is that it makes the upgrade script from the original 
custom fields schema a little more complex, but at least you would have 
custom fields, and happy users, and less squabbling, and Bugzilla 
development would gain some much needed respect.
</soapbox>



More information about the developers mailing list