We've done this since 2011 in a few projects. It might seem to not be usual for commons but if you think through then it's perfectly ok (and also acked by the board):
A GIT commit is uniquely identified by the sha1 of the parrent commit + the the diff of the commit. That's the magic why a repo can be cloned and handled independently at all. When the VOTE did pass we simply do 2 steps: 1.) propagate the staging repo to proper (and check in the source-release.zip to our dist/release) 2.) push/merge the changes to master and push it to our cannnonical GIT repo at the ASF. + push the tag as well. The sha1 doesn't change during that step, so it's guaranteed that it's the exact same as we voted on. LieGrue, strub > Am 14.11.2018 um 17:15 schrieb Gary Gregory <garydgreg...@gmail.com>: > > Per http://www.apache.org/legal/release-policy.html#host-rc it should be OK > to host the RC sources on the Apache Nexus repo instead of the dist tree. > > This is different from how we usually do RCs but is should be OK. > > Not sure about using GitHub though... > > Gary > > On Wed, Nov 14, 2018, 09:00 Mark Struberg <strub...@yahoo.de.invalid wrote: > >> PS: the VOTE is open for 72h from now on. >> >> LieGrue, >> strub >> >> >>> Am 14.11.2018 um 16:58 schrieb Mark Struberg <strub...@yahoo.de>: >>> >>> Oki, now the full VOTE text! >>> >>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1 >>> The release was run with JDK-1.7 to ensure Java7 compatibility. >>> >>> >>> The ASF staging repository is at >>> >> https://repository.apache.org/content/repositories/orgapachecommons-1396/ >>> >>> The source zip is at >>> >> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/ >>> The sha1 of the source-release zip is >> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c >>> The sha512 is >> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388 >>> >>> I added my KEY (struberg at apache.org) to our dist KEYS file >>> https://dist.apache.org/repos/dist/release/commons/KEYS >>> >>> I've created the release in a GIT manner and pushed the according >> changes to my ASF-linked github repo >>> >>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1 >>> the sha1 of the commit is >>> >> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019 >>> >>> the tag is >>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1 >>> c910171 >>> >>> This will get pushed to the ASF cannonical repo once the VOTE succeeds. >>> >>> Site will be updated once the release has passed. >>> >>> Please VOTE: >>> >>> [+1] go ship it! >>> [+0] meh, I don't care >>> [-1] stop there is a ${showstopper} (that means something _important_ is >> missing!) >>> >>> >>> Here is my own +1 >>> checked: >>> * signature >>> * hashes >>> * LICENSE >>> * NOTICE >>> * rat >>> * builds fine with various JDKs >>> >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> >>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg <strub...@yahoo.de.INVALID >>> : >>>> >>>> PS: I've created the release in a GIT manner and pushed the according >> changes to my ASF-linked github repo >>>> >>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1 >>>> the sha1 of the commit is >>>> >> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019 >>>> >>>> the tag is >>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1 >>>> c910171 >>>> >>>> This will get pushed to the ASF cannonical repo once the VOTE succeeds. >>>> Yay, this is the way GIT works and before someone not familiar with GIT >> screams that this is not hosted on ASF: This got discussed on the board >> level a long time ago (when we did DeltaSpike and CouchDB as the very first >> GIT repos at the ASF) and is perfectly fine as all this is based on >> cryptographically strong steps. >>>> >>>> LieGrue, >>>> strub >>>> >>>> >>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <strub...@yahoo.de.INVALID >>> : >>>>> >>>>> Hi folks! >>>>> >>>>> I'm currently preparing the release for commons-pool2-2.6.1 >>>>> >>>>> So far I did >>>>> >>>>> * fix the missing parts in changes.xml >>>>> * generate + copy the RELEASE_NOTES >>>>> * run the maven release (after fixing the setup...) >>>>> >>>>> The ASF staging repository is at >>>>> >> https://repository.apache.org/content/repositories/orgapachecommons-1396/ >>>>> >>>>> The source zip is at >>>>> >> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/ >>>>> The sha1 of the source-release zip is >> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c >>>>> The sha512 is >> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388 >>>>> >>>>> I added my KEY (struberg at apache.org) to our dist KEYS file >>>>> https://dist.apache.org/repos/dist/release/commons/KEYS >>>>> >>>>> I will now continue with the follow up steps and then call an official >> VOTE. >>>>> >>>>> Please let me know if something went wrong so far! >>>>> >>>>> LieGrue, >>>>> strub >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
