Hi, I'll direct everyone on this discussion thread to this pull request: https://github.com/apache/incubator-trafodion/pull/707. Perhaps we can continue our discussion there.
You can see what I propose to do and comment on it. Note that the revisions.txt file (which contains the Release History) is shared among all documents. Each document has a separate "New and Changed" information; I've only modified the one for the SQL Reference Manual. Before releasing, the same section will need changing in other manuals as appropriate. Dave -----Original Message----- From: Carol Pearson [mailto:[email protected]] Sent: Thursday, September 15, 2016 11:45 AM To: [email protected] Subject: Re: SQL Reference Manuals updates Hi, Release date is good enough, in my opinion. If someone is interested particulars, then we have that history in git, though that's developer-level function, not user-level. -Carol P. --------------------------------------------------------------- Email: [email protected] Twitter: @CarolP222 --------------------------------------------------------------- On Thu, Sep 15, 2016 at 11:17 AM, Steve Varnau <[email protected]> wrote: > I would have thought that the version of the documents (2.1) is good > to have, and the release info (release dates) should be on the web > site, rather than in the content of each document. > > The doc page > (http://trafodion.incubator.apache.org/documentation.html) > indicates that 2.0 is released, and the latest (in development) > section points to the 2.1 docs. > > The release manager task list > (https://cwiki.apache.org/confluence/display/TRAFODION/ > Create+Release#CreateRelease-UpdateProjectWebSite) > includes updating release info web page: > http://trafodion.incubator.apache.org/download.html > > But not content of the docs. > > --Steve > > > -----Original Message----- > > From: Dave Birdsall [mailto:[email protected]] > > Sent: Thursday, September 15, 2016 11:00 AM > > To: [email protected] > > Subject: RE: SQL Reference Manuals updates > > > > Hi Carol, > > > > I'm wondering if the revision date should be the date of the > > release? If so, the release manager should be the one to update it. > > > > For the moment, I've written "TBD" here. > > > > Dave > > > > -----Original Message----- > > From: Carol Pearson [mailto:[email protected]] > > Sent: Thursday, September 15, 2016 10:58 AM > > To: [email protected] > > Subject: Re: SQL Reference Manuals updates > > > > Hi Dave > > > > It seems like the "update the revision history" step should be part > > of > the > > release manager checklist that Roberta and Steve put together? > > Nobody knows if s/he is the last person to update it.... > > > > The alternative is every update is presumed to be the last, so each > person > > updates it as part of the change.. > > > > -Carol P. > > > > --------------------------------------------------------------- > > Email: [email protected] > > Twitter: @CarolP222 > > --------------------------------------------------------------- > > > > On Thu, Sep 15, 2016 at 9:13 AM, Dave Birdsall > > <[email protected]> > > wrote: > > > > > Hi, > > > > > > > > > > > > I’m about to add documentation to the SQL Reference Manual for the > > > incremental UPDATE STATISTICS (IUS) feature for Trafodion 2.1. > > > > > > > > > > > > I’m guessing I’m the first person to do so for this release. > > > > > > > > > > > > One thing I notice is that the Revision History doesn’t have an > > > entry for 2.1. I propose to add one, with a notation that this is > > > a work in progress. > > > The last person to update before the release should remove that > > > note and set the date of the release. > > > > > > > > > > > > Section 1.2 New and Changed Information appears to have stuff for > > > the previous release (2.0, 2.0.1). I propose to remove all of > > > this. But will add an entry for incremental update statistics. > > > > > > > > > > > > Does this sound right to you? > > > > > > > > > > > > Are there other general sections of this kind that need updating > > > for the next release? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Dave > > > >
