The Road to 2.18
stu at asyn.com
Sun Mar 7 23:41:06 UTC 2004
Mark Davis wrote:
> Christian Robottom Reis wrote:
>> On Fri, Mar 05, 2004 at 07:52:34PM -0500, David Miller wrote:
>>> I'd like to propose that we do our feature freeze for 2.18 on March
>>> That's a little less than a week and a half from now. Is this too soon?
> What are the odds of 91037 making it in to 2.18? I've been working
> with a patched 2.17.6 and have been please with the base
> functionality, but there are a couple of things that still need to be
> worked if the custom fields are to be first-order fields.
> The biggest problem we are having is getting the new fields to appear
> as list boxes on the query page... I hope to be able to work on this
> in the coming week, but I'm not certain if the patches in the bug are
> in a state to be merged with CVS in included in the next major release.
It would be a big win from the users perspective to get even a partial
solution towards custom fields get into the system for the next release.
This would lock-down a supported schema with a migration path in case
the approach were to change. All these caveats about applying the custom
fields patches because there is "no guarantee that this will be the way
we do it" are holding some people back from trying it out.
More information about the developers