[development] Code freeze?
shai at content2zero.com
Thu Jun 26 07:29:55 UTC 2008
Dries and all,
I think it is only natural that Drupal's success will lead to slower
Most Drupal shops will only begin creating Drupal 6 production sites this
summer. There will be so much learned from creating productrion sites in 6.
That learning should be taken into account when coding for 7.
In my opinion, what is key for Drupal to stay true to its core values is
that major upgrades remain open to significantly changing APIs where they
lead to improvements in the platform. That will keep Drupal fresh and
compelling. There don't need to be yearly major releases to keep Drupal
I can also imagine that it might be in Acquia's interest to slow down
development cycles. Though Acquia's interests may not always be the same as
Drupal's, I think often they are. I don't think there is anything wrong with
adjusting development cycles or other plans based on Acquia's interests.
I know you didn't a mention a date for the code freeze. I'd vote for Spring
On Thu, Jun 26, 2008 at 3:08 AM, Dries Buytaert <dries.buytaert at gmail.com>
> I've been thinking about this some. While we have made incredible progress
> with the test infrastructure as well as implemented a dozen of usability
> improvements, we're still light on feature improvements (such as fields in
> Combined with the late arrival of CCK and Views, and the many Drupal 6
> books that are currently being written, it sounds best to postpone the code
> freeze a little longer. Given the current state of things, the proposed
> July 15 deadline seems a bit too aggressive to my liking.
> If people are supportive to the idea of pushing back the code freeze date,
> I'll write up an announcement.
> On 24 Jun 2008, at 10:36, Augustin (Beginner) wrote:
>> What is the latest news about the D7 code freeze. I haven't seen any
>> announcement on this list. Do we have a date for the code freeze, or
>> at least a better estimate than what was offered at the beginning of
>> the thaw?
> Dries Buytaert :: http://buytaert.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development