Kiall Mac Innes wrote:
The Drupal document referenced is not explaining "How to develop Drupal" but rather
"How to develop a drupal based site using git".
Actually in my book that is one of the same thing once we move to more complex
sites. Parts of my own sites ARE packages under development in parallel with the
main code tree, and while developing one invariably bugs are fixed in the main
tree which need to be pushed back. This is precisely why I needed DVCS here, and
managing and updating sites via Hg is working well.
Drupal does have several documents on how to contribute fixes/features
to Drupal itself
Actually the whole documentation tree is looking pretty good
http://drupal.org/documentation/git
But it still does not convince me that I made the wrong choice switching to Hg,
and I can still pick up anything I want from the Drupal repos anyway.
At the end of the day, it's the whole infrastructure that needs to be agreed on,
and I suspect that the Drupal model could be simply cloned into php.net?
Irritating for some of us, but it can be lived with. I just think that it's a
bit like Windows - everybody uses it despite it's faults - and simply work
around it's faults. For me the very poor cross platform integration and support
in Eclipse was a show stopper several months ago, so my own base is now Hg.
--
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
