I'm fine with it, but you better okay with Cris, since this is his turf ;-)
Now, what's the deal with updating the docs? Obviously the Wiki can be
updated more frequently than code releases. Should we not be doing that?
The reason I ask is that the original modeler docs had a lot of holes that
I intend on filling and other stuff that just needs to be updated. I
don't want to be ripping docs out from under people's feet, but I'd
imagine enhancements aren't a problem, correct?
-- KevinOn Tue, 07 Mar 2006 05:05:06 -0500, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Cris, Kevin -- > > I just finished the first cut of the nested DataContext commit > functionality and wanted to make a release. I was wondering how close > are we to using CAYDOC Wiki space for release documentation. I recall we > had these unresolved issues: > > 1. Smart hyperlinking to JavaDocs (IMO we can ship the docs with this > not fully resolved), > 2. Table of Contents. We want it to be off for the PDF export and on for > the HTML. I guess we can go with PDF only option in M12 (and temporarily > remove sample ToC from the Deployment section)?? > 3. ... anything else I am missing?? > > An unrelated question. Cris, I was going to merge all stuff under here: > > http://objectstyle.org/confluence/display/CAY/1.2+User+Guide > > to CAYDOC user guide. Wanted to check if this would interfere with your > work and whether I should hold it off for now. > > Andrus
This archive was generated by hypermail 2.0.0 : Tue Mar 07 2006 - 08:00:34 EST