[development] Patches - code freeze

[Larry Garfield]

On Wednesday 23 May 2007, Dries Buytaert wrote:
> *** Larry wrote in another thread:
> > In addition to claiming modules to work on, if there are any
> > pending patches that make substantial changes to a core module that
> > need to go in before code freeze let us know about those, too, so
> > we can not touch that module yet.  This performance refactoring can
> > stretch post-1 June I believe since there's no API changes (Dries,
> > correct me if that's an incorrect statement), and I'd rather not
> > block someone else's patch that's almost-there. :-)
>
> There are a lot of patches really, and we could use a hand reviewing
> those.  And when I say "reviewing", I mean "studying the code and
> thinking it through" rather than just showing your support to the
> author of the patch.  We could use more "in-depth reviews" to help
> some of the bigger patches move forward.

*snip*

I'm going to interpret that as "splitting stuff up can wait," then, and see 
where else I can be useful. :-)

-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson