I guess it depends on how frequently you maintain your projects. I've
got some that require weekly maintenance and others that won't change
for months. It seems easier for me to publish a project 'snapshot'
and know that further updates to the Zend Framework won't break them
unexpectedly or require a lot of work to bring it back into line - a
good example here is two projects I have with the new MVC and a whole
bunch of others that aren't. It would allow me to maintain all sites
with my own framework additions and not need to worry about major
rewrites too often (Zend_Config, for example! :-)
Thanks for the heads-up Darby
I considered this method myself for my own projects, but the amount
of time it would take to the normal checkout/update/commit cycle
seemed a bit excessive. Additionally, in this thread, we'd have to
deal with two separate branches of the entire framework - library
under both trunk & incubator.
Perhaps for a release that is pegged to a specific tag, it would
make more sense, but for development, it seems like an awful lot of
work. Am I being too critical?
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
4124
http://www.peptolab.com
