Hi Jason, Sorry for the delay. Please see my comments below.
Jason Stewart <[EMAIL PROTECTED]> writes: > Just for clarification. The Forrest system is mostly a superset of > what stylebook provides. The irritating part is the index file > organization has changed - otherwise it would simply be a perl script > to change the sb tag names to forrest tag names. Hm, I am now wondering why are we migrating to Forrset then? I thought the idea was to replace the document system with something better and more structured, and possibly redesign the appearance of the site to look more modern? > > Sure. What I meant is we shouldn't make any hard dependencies between > > code releases and porting to Forrest until all the infrastructure- > > related work is done and the migration path is clear and worked out. > > This way, if the person with the expertise is suddenly unable to > > finish the work, we won't be stuck with something half-done and > > unable to move forward with the code base. > > Hmm... > > OK. So you want the new forrest site to be 3.0 specific? I am not sure what you mean by "3.0 specific" but I don't think that's what I meant ;-). My point is we shouldn't make any of the source releases dependent on the Forrest migration until it is clear it can support our needs and the migration plan is worked out. Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
