Hi,
This is related to my earlier mail re. the oak-doc module [1].
Our releases currently contain "snapshot artefacts" of oak-doc and
oak-mk-perf as can easily be verified by looking at the content of the
recent 0.20.0 release [2].
How should we handle this for the upcoming 1.0 release? Should we just
exclude those or should we bump their versions?
For oak-doc my preference would be to bump it to 1.0 and merge all
relevant changes from trunk so the 1.0 branch so Oak 1.0 would come with
its own documentation self contained. On the website [3] I would like to
continue to publish the documentation from trunk and update it once in a
while. This way we could always point people to the released versions
for the respective documentation and continue having bleeding edge docs
on the website. I think this approach best balances the effort of
maintaining the docs with having the correct docs available once Oak
evolves further.
Michael
[1] http://markmail.org/message/mof6pqqmwkth7osc
[2]
http://www.apache.org/dyn/closer.cgi/jackrabbit/oak/0.20.0/jackrabbit-oak-0.20.0-src.zip
[3] http://jackrabbit.apache.org/oak/docs/
