Gary Shea wrote:
In principal - any time you update from CVS the result should build. I basically try to add and validate new stuff before committing. For example, the current CVS should be fine (providing you update your avalon-framework CVS becasue there we changes there a few days ago, and alos you need to update the excalibur/meta - as I've been finalizing some thing there over the last few days).Hey Steve, just wondering what your CVS-state policy is for merlin. Do you intend that the CVS version always be functional, or are there tags for latest functional version? I've been avoiding tracking the CVS too closely for fear of getting a non-functional snapshot, but it would be nice to stop worrying and start updating!
I.e. stop worrying and start updating!
Cheers, Steve.
Gary
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
