[development] Code freeze?
sirkitree at gmail.com
Thu Jun 26 13:23:48 UTC 2008
Agreed on the later code freeze, and I definitely think next summer is not
unreasonable. Coming from an in-house shop with large installations who are
struggling to get a D6 upgrade still in the works almost solely because D5
might not be supported (okay the cooler features of the framework are a huge
incentive to the devs) it's slightly intimidating to think that there
already be a code freeze on the next version of Drupa when we *might* have
D6 upgrades done by the end of October. Many modules have still not caught
up (mine being some of them) making it very hard to get full platforms up to
speed with D6. So yes, many reasons from an in-house perspective to have
longer development periods. +3 (taking into account my colleages aren't on
this list but feel the same).
On Thu, Jun 26, 2008 at 8:03 AM, Wim Leers <work at wimleers.com> wrote:
> Here's another confirmation of that seemingly unified sentiment. It seems
> to me nobody has had enough time to *really* start working with D6. I also
> still have to port several relatively popular modules, and for me too, they
> are a higher priority than contributing to D7. So, I'm also for a delay of
> the code freeze.
> Wim Leers ~ http://wimleers.com/work
> On Jun 26, 2008, at 12:04 , Robert Douglass wrote:
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development