Re: [SQLObject] Re: Moving docs around

[Ian B. <ia...@co...>]

Jorge Godoy wrote:
> Kevin Dangoor <da...@gm...> writes:
> 
> 
>>I came to roughly the same conclusion for TurboGears. I am generating
>>the site from the trunk, but marking the unreleased portions. Though
>>the site is generated from the trunk, the documentation does still get
>>branched/tagged with the code. So, if you go back to an old version,
>>you can also see the corresponding site from the time. (Whether that's
>>useful or not remains to be seen... I was just pointing out that I've
>>left the code and docs together rather than separating out the
>>docs...)
> 
> 
> I also believe this is better (keeping docs and code together).  From other
> projects of mine, this was the best way to obtain information about one
> specific version, otherwise you'd have to keep a map like "revision X of code
> corresponds to revision Y of documentation minus notes A, B and C"... 

I can tag the documentation at the time of release.  However, the issue
is that current documentation is often more accurate with respect to
older versions than is the documentation in those older versions.  But I
just can't bring myself to go through the effort to backport
documentation fixes.


-- 
Ian Bicking  |  ia...@co...  |  http://blog.ianbicking.org