After thinking about this further, I've come to the conclusion that
the vendor branching approach really is the best (and correct) way of
managing SVN, cake updates, and even your own personal libraries.
Grant Cox wrote an excellent article about this in the bakery.
http://bakery.cakephp.org/arti
After thinking about this further, I've come to the conclusion that
the vendor branching approach really is the best (and correct) way of
managing SVN, cake updates, and even your own personal libraries.
Grant Cox wrote an excellent article about this in the bakery.
http://bakery.cakephp.org/arti
I don't store the Cake core code in my project's SVN repository
either. To upgrade, I just do an svn update on the cake directory I
am using for my project. If something in the upgrade doesn't work I
can either:
-- backtrack the cake core
-- fix my project's code to work with the new core
-- in
Are you saying you do not store cakephp in SVN as a separare "vendor",
ie. you aren't using vendor branching?
How do you handle cake upgrades? Do just replace the latest cake core
folder into each project and recommit to SVN?
Am now wondering whether vendor branching is overkill, since I don't
c
