On 2018-06-21 11:26, Davide Giannella wrote:
On 20/06/2018 15:13, [email protected] wrote:
+7. If this is a stable branch, review changes to export versions which should
be avoided (see [OAK-6346](https://issues.apache.org/jira/browse/OAK-6346) for
context). Example: review the output of the command below for any changes of
`package-info.java`.
+
+ # Oak 1.8 as of June 2018
+ svn diff .
https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.4
Agree on this of course. However a manual review is always very error-prone.
Aren't there any tools to cross-check this aspect? Possibly maven that
could e plugged into the `release` profile so that it will fail the
release if anything change? Or even better enabled by default so that it
will fail any build?
Well, the question is whether we always want to fail it in this case...
