On 17 April 2011 07:17, Philip Olson <phi...@roshambo.org> wrote: > Are people still thinking about this? And how about applying the > current/revised patch to trunk thus making it easier to play with and break, > but not freeze its features/API yet.
As much as I like this idea — and I really, genuinely, enthusiastically* do — allow me to open the can of worms and repeat a question I've asked periodically on IRC and IRL (with varying levels of directness) over the last few months: Is there any thought that we might stop throwing things into trunk soon and start thinking about some sort of release? 5.3.0 came out in June 2009. Even if we start the alpha process now, there's no chance trunk is going to hit stable until the last few months of the year, so we're looking at over two years between minor releases, which is about as long as I'd be comfortable leaving it — not just for any PR reason, but because there's some genuinely good stuff in trunk that I think deserves to see the light of day. I mean, if people want to continue experimenting, that's great, but should we be factoring this into the thought process, at least? There's nothing stopping a 5.4 branch being created earlier than has been traditional (say, alpha 1 or beta 1) and letting development continue on trunk. In effect, we'd simply be reverting to the three branch model that's existed for most of the last few years. Sorry to hijack the thread, but I think the question needs to be asked. Anviliciously yours, Adam * You can insert more adverbs if you like. I am very +1 on this feature. I use the equivalent feature provided by Django for development all the time, and it's amazingly handy. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
