To fulfill this requirement even having gitbox SCM URLs in our pom.xml would not suffice. Instead during the release one would need to do a fresh checkout from gitbox locally before building the release, because release:prepare does not do that[1]. Instead prepare just takes the current working directory as source.
[1] - http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html > On 10. Oct 2017, at 12:09, Bertrand Delacretaz <[email protected]> wrote: > > Hi, > > On Tue, Oct 10, 2017 at 12:06 PM, Konrad Windszus <[email protected]> wrote: >> ...I think as long as the ASF is fine with this I would also rather promote >> the usage of Github instead >> of gitbox (because of its richer feature set) and therefore I am finally >> convinced that entering the Github >> SCM URL is fine there.... > > I'm fine with that in general but cutting releases from ASF > repositories is a strong requirement. > > Worst case we could add instructions to our release process, using git > diff to compare the ASF and GitHub repositories before cutting a > release. > > -Bertrand
