> Now is a good time to split off from 10.5. Like a few others have said, > blocks is a large improvement, which simply cannot be used when supporting > 10.5 and xcode 3.x. I think it cannot be stressed enough about how bad an > idea this is in a resource deprived scenario. You are proposing a large > misuse of resources here, and don't have anything really compelling other > than "but we said we'd do it in a meeting!" and "it's in this policy!". I > think you really should look at what you are proposing here Robert, I don't > think it's right to the people writing the code to force them to do what > they don't want to do here.
How is this any different from supporting 1.4.x? No one wants the giant behemoth that 1.4 was, so releasing 1.5 soonish would also count toward a shorter release cycle, as I believe most people on the list would favor. And from a technical support point of view, I don't assume that this would make much of a difference, given the size of the current 1.5? I certainly understand what you are saying, but putting 1.5 on a feature freeze in say, one month, would get it out the door before Lion (I hope!). Then 1.6 could be targeted for dropping 10.5 support and branched of immediately, so that people could work on it if they prefer so. -David Munch
