Tapestry documentation should clearly/boldly identify the release number
------------------------------------------------------------------------
Key: TAP5-357
URL: https://issues.apache.org/jira/browse/TAP5-357
Project: Tapestry 5
Issue Type: Bug
Components: documentation
Affects Versions: 5.0.16
Reporter: Howard M. Lewis Ship
I hate to flag every change with a release number, but a good start would be to
have the release number matching the documentation present on every page of the
documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]