> I'm just concerned that some people may remain "bruised" from the recent > cvs problems that came about from upgrading the build.
I think as long as we decide/vote to go a specific trail there is no reason to be "bruised" whether it is unpleasant for a while or not. At least for HEAD :) > If anyone has a > problem with in-process Forrest files in the Cocoon cvs, we can adjust > course and pursue a more cvs-sensitive approach. No problem > Still, I think I may be > too conservative about these things. Perhaps the best thing is to simply > throw it in the cvs and let everyone help finish the work -- as is > happening right now. Doesn't sound too bad :) ...just go ahead -- Torsten
