Josh Berkus <josh@agliodbs.com> writes:
> One thing Peter forgot to mention here is that the next-to-last
> commitfest is the *last* commitfest for new major features. For the
> *last* commitfest, any patch introduced either has to be a resubmission
> of something we've seen at a prior CF, or has to be very "small" (i.e.
> not many lines/files, no side effects, no API or defined standard API).
We've been kicking around variations of that idea already.
As I mentioned in the core discussion, I'm a bit concerned that this
would have the effect of choking off development too soon. We could
have a situation where nothing major is supposed to be getting worked
on from Nov 15 to mid-May, which seems much too long. So "very small"
seems too strict. Robert's suggestion of a 1000-line cutoff might be
workable though.
regards, tom lane
