David Soria Parra wrote:
I'm not sure choosing DCVS by vote is actually a good way to go here.
> I think we need much more input from people that maintain all the
> infrastructure we're using now and would be doing the move. If we
> don't have people committed to making it happen majority-based vote
> is useless IMHO.
Sure. I wrote the RFC because I plan to implement it. I will make it
possible for either Git or Mercurial, but as stated, I prefer doing it
with Mercurial.
The vote is not a 100% we do it, but rather a: we would like to have it
that way. So if people choose Bazaar, someone has to come up with a
solution.
I think the problem here is that _if_ the majority are already committed to git
anyway, those of use who are using hg or something else are going to be at a
disadvantage since it is now obvious that cross working will not work especially
if everything is rolled into the one super repo.
Even the 'decision' to roll everything into single repo copying the current SVN
history _should_ be something that is put to a vote. The problems of testing
_sections_ of this vast code base and tracking bugs against them should be a
perfect reason for a much more modular approach so we can test each module as a
separate package. And the process is something that _does_ change depending on
the different DVCS's. So simply voting on the current rfc seems a little
pointless at the moment?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
