what about this: Currently mvn release and mvn upload will always send the release to nexus,
So what about: - we provide an script to artemis to download the correct bits of the release, the release manager would use that script to perform such download. - The release manager would place it on the dev repository Robbie is mentioning... (that means.. we wouldn't really have an extra step). On thing I'm not sure how to do is... how to upload it to the dev dist at https://dist.apache.org/repos/dist/dev/activemq/ and how we would make the final move? just a regular copy? On Wed, Sep 13, 2017 at 9:49 AM, Robbie Gemmell <[email protected]> wrote: > On 13 September 2017 at 14:35, Clebert Suconic > <[email protected]> wrote: >> On Wed, Sep 13, 2017 at 9:21 AM Robbie Gemmell <[email protected]> >> wrote: >> >>> This was less about time, though there is some benefit in that regard, >>> with how much depending on how particular people actually verify the >>> checksums I guess. >> >> >> >> Actually this is kind of moot. nexus does that check for you. You cannot >> upload a release with a checksum broken. It won't let you close. >> >> Like. Last week I had to restart the release once because MVN upload broke >> the checksum somewhere. >> -- >> Clebert Suconic > > Whether the files in Nexus are ok isn't sufficient. The archives and > checksum files in the dist repo are the mirrorer official release > artifacts (and strictly only the source ones at that), and Nexus cant > check those. There could be a problem deploying those bits for a > variety of reasons, so we check they are ok. Users downloading the > release archives also tend to grab the checksums from the dist repo > because that is their official source, in order to verify downloads > that have come from the third party mirrors which dont store the > checksums for obvious reasons. > > Robbie -- Clebert Suconic
