db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scott hutinger <S-Hutin...@wiu.edu>
Subject [doc] website alpha docs old (April 2005)?
Date Thu, 13 Oct 2005 16:28:56 GMT
I was looking at the latest file; which follows this text:

I downloaded the gettingstarted alpha pdf, and it had a build tag date of
Derby Document build: 2005-04-12T11:30PST : 12 April 2005

In fact, ALL the alpha docs are dated April 2005.  I was under the 
impression that the alpha docs were built whenever changes were found in 
some automated build procedure :-)  I guess this is wrong.

1) Can we update the Docs?
2) When are the Docs built and published?

Can we fix or get something in place that will fix this problem in the 
future?

thanks,
scott

[srh@scott trunk]$ svn up
U  src/adminguide/cadminappsclienttracing.dita
Updated to revision 320792.
[srh@scott trunk]$ svn log src/adminguide/cadminappsclienttracing.dita
------------------------------------------------------------------------
r279553 | bakksjo | 2005-09-08 05:59:59 -0500 (Thu, 08 Sep 2005) | 1 line

Fixes DERBY-544: Admin guide has wrong value for constant 
TRACE_RESULT_SET_CALLS. Contributor: Oyvind Bakksjo <oyvind.bakksjo@sun.com>
------------------------------------------------------------------------
r226700 | noel | 2005-07-31 18:30:43 -0500 (Sun, 31 Jul 2005) | 1 line

move Derby from Incubator to DB
------------------------------------------------------------------------
r208694 | fuzzylogic | 2005-06-30 18:12:01 -0500 (Thu, 30 Jun 2005) | 4 
lines

DERBY-381: Changes for review of Derby Server and Admin guide.

Committed for Jeff Levitt <derby@mylevita.com>

------------------------------------------------------------------------
r202296 | fuzzylogic | 2005-06-28 17:46:15 -0500 (Tue, 28 Jun 2005) | 23 
lines

Derby-394: Improve formatting and presentation of the documentation.

1. Added more related links. DITA can dynamically create related links 
separated   by conceptual info, task info, and reference material to the 
bottom of each
   page of each book. This means that not only does it place a link to the
   parent topic of each file, but it also adds sibling links and 
children links.   When I originally created the DITA files for these 
books, I didn't account
   for this.

2. Implemented use of the <shortdesc> tag. If we separate the first few
   sentences of each topic from the rest of the content by placing them in a
   <shortdesc>, the result is that if the parent topic or any siblings 
have a
   link to that topic generated by DITA, then the content in the 
shortdesc tag
   is also pulled and used as a summary of the topic.

3. Improved badly-formed tables.

4. For the Server and Admin guide, editorial changes such as fixing grammar,
   spelling, and punctuation, removal of italics and bold type where it 
wasn't
   needed, and removal of empty topics.

Committed for Jeff Levitt <derby@mylevita.com>

------------------------------------------------------------------------
r191746 | jta | 2005-06-21 18:39:52 -0500 (Tue, 21 Jun 2005) | 3 lines

DERBY-373 Applied Jeff Levitt's patch that fixes documentation errors in
the Server/Admin Guide.

------------------------------------------------------------------------
r170064 | fuzzylogic | 2005-05-13 13:08:19 -0500 (Fri, 13 May 2005) | 2 
lines

Switch "..\dtd\.." to "../dtd/.." to prevent build breakage on Unix 
platforms.

------------------------------------------------------------------------
r170061 | fuzzylogic | 2005-05-13 12:48:38 -0500 (Fri, 13 May 2005) | 5 
lines

Remove the <?pub caret?> tag from any files that had that them. The presence
of this tag was causing the doc build to fail on some unix platforms.

Committed for Jeff Levitt <derby@mylevita.com>

------------------------------------------------------------------------
r168976 | jta | 2005-05-06 17:46:20 -0500 (Fri, 06 May 2005) | 1 line

Committing patch for DERBY-261
------------------------------------------------------------------------


Mime
View raw message