Manual and Guide Versions in the documentation
sunfish62 at yahoo.com
Tue Aug 3 20:46:46 EDT 2010
--- On Tue, 8/3/10, Tom Bullock <tbullock at nd.edu> wrote:
> From: Tom Bullock <tbullock at nd.edu>
> Subject: Manual and Guide Versions in the documentation
> To: "John Ralls" <jralls at ceridwen.us>
> Cc: "gnucash-devel gnucash" <gnucash-devel at gnucash.org>
> Date: Tuesday, August 3, 2010, 2:23 PM
> Message: 8
> Date: Mon, 2 Aug 2010 12:50:20 -0700
> From: John Ralls <jralls at ceridwen.us>
> Subject: Website Links
> Also, the online manual and guide seem to be for 2.0; it
> should be updated to 2.2.
> John Ralls
> Your comment raises the question: What is the
> process/method that documentation version reporting should
> Looking at the little I have been working on in the Guide,
> the top-level NEWS module shows a history of version changes
> ending at version 2.0.1 dated 10/08/2006. Before that,
> leading up to that point, there is a trail of version
> changes and implementation dates (I infer) with a brief
> comment about reason for entry.
> Since the documentation seems to be behind installation of
> new features, is there a way to identify the features added
> since the last point at which the documentation did match
> the feature install? If that can be figured out, then that
> provides a "to-do" list for documentation updates (I
> assume). It also would suggest the order that patches should
> be added, if documenting in the order of oldest to newest
> feature first.
the main Gnucash page (www.gnucash.org) includes release announcements that include substantial lists of changes from version to version. I don't know if the lists are exhaustive, but they are sure exhausting to wade through.
There may be a better way to get this information, since I believe it's culled from svn somehow.
> Your thoughts and anyone else's experience would be much
> appreciated to define the scope of what is needed.
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
More information about the gnucash-devel