search

google-code-export / h2database

Automatically exported from code.google.com/p/h2database
0 stars 1 forks source link

Since release/build in documentation #301

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Because H2 documentation is constantly evolving like H2 itself it becomes 
difficult to determine what features apply to what versions unless you track 
svn head.  Would it be too much trouble to start documenting "since build 152" 
on each updated feature/grammar in the documentation?

Original issue reported on code.google.com by James.Mo...@gmail.com on 11 Mar 2011 at 3:34

GoogleCodeExporter commented 9 years ago 
That would be possible, but it would also make the documentation unreadable. 
There would need to be a way to hide that data (and it should be hidden by 
default). Also, it shouldn't affect development too much. There is already 
enough bureaucracy. If possible, I would rather simplify / streamline the 
development process. 

Ideas are welcome! Maybe something based on "svn blame"?

Original comment by thomas.t...@gmail.com on 11 Mar 2011 at 5:48

GoogleCodeExporter commented 9 years ago 
Setting to "won't fix" at the moment.

Original comment by thomas.t...@gmail.com on 25 Mar 2011 at 7:24