Now hold on a sec - It's ok to vote to determine the fate of PHP
development - for the entire PHP-lovin' world.
Yet, it's not ok to vote for the handful of developers to collaborate?
Three weeks of discussion (based on what I've seen here on the list)
seems not enough for such a heavy change.
Point in case - it's still being discussed right here; right now. But I
agree with the direction: try the contenders out.
I understand there's complications such as scripts and automation, but I
hope they aren't the reason for impeding progress.
Sticking with a system for 'a long time' results in just as many battle
scars - if not more than keeping up with the times (conservatively).
On 8/25/2011 1:12 PM, Kalle Sommer Nielsen wrote:
2011/8/24 David Soria Parra<d...@php.net>:
Hi Internals,,
after 3 weeks of discussion, I think we are ready to start voting on
the DVCS RFC. If you think something is missing or should be explained
in more detail, let me know.
I won't transfer the discussion over here but; I don't want to move to
a new system we we did it just a few years ago, as Rasmus said long
before we moved was that we want to find a solid system that could
hold out just as long as the old setup. I don't have a problem by
using SVN, nor merge as we have been good at keeping files in sync so
its easy to merge patches, much easier than the old unicode-trunk.
That being said; I agree with Stas that having a vote is not a good
way to actually make a choice here, but it gives a hint of those that
voted, as I'm sure that there are many more actively working on the
project like PEAR. PECL and Doc guys thats not gonna vote because they
don't follow Internals.
But -1 from me.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
