[development] Code freeze?

[Robert Douglass]

Just to confirm what seems like an overwhelmingly unified sentiment: a  
later D7 seems like a good thing. We started a bunch of work on the  
search system at the search sprint in Minnesota and I'd really like to  
see the bulk of it get finished. Yet I'm still sitting on relatively  
popular modules that I have to upgrade to D6 and I can't help but  
think that they are a bigger priority for me at the moment. Delaying  
the date of the code freeze just seems like the right thing.

- Robert


On Jun 26, 2008, at 11:36 AM, Nathaniel Catchpole wrote:

> I'd also like to see a much later code freeze. At least November  
> 15th - but the first half of next year also sounds good.
>
> Testing has come a long way, but time spent on that has slowed down  
> development of features (and in my own case time spent using D6 and  
> helping get modules upgraded for that) - on my part this is betting  
> on a longer D7 release cycle, so there'll be a longer period to get  
> these things in later - so I really hope that plays off...
>
> There are also Summer of Code projects which directly impact quite  
> neglected parts of core (new help system, new aggregator etc.) -  
> delaying the code freeze might give these a chance to develop into  
> core patches - but it'll be a long wait to get them into Drupal 8.
>
> Since testing is generally working to keep things pretty stable, we  
> should be able to have a much, much shorter freeze/beta/rc period -  
> and much less incentive for people to try to push patches in at the  
> last minute.
>
> And there's no D7 maintainer yet - wouldn't be fair to only let them  
> commit patches during code freeze would it?
>
> Nat
>
>