Stalled custom field development

Maxwell Kanat-Alexander mkanat at bugzilla.org
Fri Apr 1 00:05:56 UTC 2005


On Thu, 2005-03-31 at 14:11 -0500, Christopher Hicks wrote:
> The official process of small 
> patches seems to be sort of like the Hippocratic Oath for software. 
> While this is an admirable thought, part of the beauty of software is 
> being able to break it and fix what doesn't work.

	(1) That's what we did for 2.18, and look how long it took us.

	(2) I don't know if you've looked at the basics of Sean's patch, but it
*replaces* Search.pm with a brand-new module. That's not an acceptable
change for a single patch. :-)

	The best way to have bad code in Bugzilla that stays around for a long
time is to check in large patches.

	We *can* have Custom Fields for 2.22, and I'm planning on it. We just
need somebody to start now working on the blockers that I've posted,
nearly all of which can be worked on now.

	-Max





More information about the developers mailing list