Re: [ALL] SHA256/512 hashes
On Sat, 25 Aug 2018 19:05:55 +0200, Stefan Bodewig wrote: On 2018-08-25, Gilles wrote: On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote: On 25 August 2018 at 09:48, Stefan Bodewig wrote: On 2018-08-25, Gary Gregory wrote: Is what you are referring to for a different purpose? Probably for those who don't want to use the release plugin :-) But yes, it could be used as an alternative hashing method. I thought that the release plugin was intended for all components to converge on the same release "recipe"... That's not my understanding. We vote on the release artifacts; how these are created is up to the release manager. The release plugin offers a way to make releases easier but it is never going to become the only permitted way of cutting releases. It's not what I meant either, even if it ultimately would become the preferred, easy and fool-proof, way. The suggestion is more on sub-project configuration (POM) convergence. Regards, Gilles Stefan - 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
Re: [ALL] SHA256/512 hashes
On 2018-08-25, Gilles wrote: > On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote: >> On 25 August 2018 at 09:48, Stefan Bodewig >> wrote: >>> On 2018-08-25, Gary Gregory wrote: Is what you are referring to for a different purpose? >>> Probably for those who don't want to use the release plugin :-) >> But yes, it could be used as an alternative hashing method. > I thought that the release plugin was intended for all > components to converge on the same release "recipe"... That's not my understanding. We vote on the release artifacts; how these are created is up to the release manager. The release plugin offers a way to make releases easier but it is never going to become the only permitted way of cutting releases. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.4 based on RC1
+1 - Release notes typo: commons-release-plgin -> commons-release-plugin - https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.4-RC1/site/index.html: Update the version number in the example POM from 1.1 to 1.4. - https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.4-RC1/site/changes-report.html: Set the release date >From src zip: ASC, SHA256, SHA512 OK. RAT check OK Clirr check OK mvn clean package OK with: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T12:33:14-06:00) Maven home: C:\Java\apache-maven-3.5.4\bin\.. Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_181\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Gary On Fri, Aug 24, 2018 at 7:56 PM Rob Tompkins wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Release Plugin 1.3 was released, so I would like to > release Apache Commons Release Plugin 1.4. > > Apache Commons Release Plugin 1.4 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.4-RC1 > (svn revision 28953) > > The Git tag commons-release-plugin-1.4-RC1 commit for this RC is > 9a3d7d06d327010d1ecb02740f9f266b8d089d8e available at: > > https://git-wip-us.apache.org/repos/asf?p=commons-release-plugin.git;a=tag;h=refs/tags/commons-release-plugin-1.4-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1374/org/apache/commons/commons-release-plugin/1.4/ > > These are the Maven artifacts and their hashes in Nexus: > > #Nexus SHA-1s > commons-release-plugin-1.4-test-sources.jar > (SHA1: 0ca6c715a7acecb33b7ad9b789d8a3e93b0209d0) > commons-release-plugin-1.4-javadoc.jar > (SHA1: 3c01989243e369c5f41c44a2be6d762ff18425a4) > commons-release-plugin-1.4.jar > (SHA1: d20aeea344ac3dc9711672795e105c7eee626250) > commons-release-plugin-1.4-tests.jar > (SHA1: 4026247744c4213148f1b0ce003ecfed1218d760) > commons-release-plugin-1.4-sources.jar > (SHA1: 9cf4cd1c2770a3c0c9159c7f8ddd61c83295648e) > commons-release-plugin-1.4.pom > (SHA1: 6106d7aedb0c3039c257e5aa706f3324a7f6ad06) > > #Release SHA-256s > #Fri Aug 24 21:35:00 EDT 2018 > > commons-release-plugin-1.4-src-tar.gz=4bf738811077b540877fdfff9b2e75db54b87bc3d7fa8b8081436e2bd3b313ea > > commons-release-plugin-1.4-bin-tar.gz=2f50e2474204bf0bc38dd421889a4298946d17c2a770675517d99bfad495512e > > commons-release-plugin-1.4-src-zip=8ef5ed89c0526d89689b27d42d914bee014a653ad02d7a4614bccb24885e5635 > > commons-release-plugin-1.4-bin-zip=5b8571444cdf786ab2307e51348af2e5550bfb26d34ece8e39c9dc7e2a44152a > > commons-release-plugin-1.4-javadoc-javadoc=3521acb9149a7d3ba20955c550284c16c825ff0590904383cd1c427a2292c7ef > > commons-release-plugin-1.4-test-sources-java-source=e3bde9b9afb5faf7b9d52335fe6273560c469e4485cf8017c37e30bcd17f5b52 > > commons-release-plugin-1.4-sources-java-source=85b2010440c2b287ff63907fdcb089fae26177c7ddcc0956857dcb7aef39796e > > commons-release-plugin-1.4-tests-test-jar=bdb2605531ea390cca2e014d8e6e016cccac2978dae27e494ce30c81192c7d99 > > #Release SHA-512s > #Fri Aug 24 21:35:00 EDT 2018 > > commons-release-plugin-1.4-src-tar.gz=1360dde9c30b317d42ed576221d896c0a999a95748aeaeb653be7ac5700b2116ff16ab682a996f7e9351773522ebdca9744bb2e22191ad79ae46049cd84b1fb6 > > commons-release-plugin-1.4-bin-tar.gz=114cb577027deb84291d6514c9728f4c50c7b50e6cff4fa37a79a3161a89f23e6d815e69cab5ec0a7f5926e5883a4b78ec72f497b764a45af2a63b33f772f153 > > commons-release-plugin-1.4-src-zip=51c699d7dd75bb26d6199af11c5d75fbc3c3710a9cc3807e62f46a9329bfda989a32ac21b057ebf690bcd7a4a3da68f23d4da4283a4d7c2d50ac0ffddfa8d1a0 > > commons-release-plugin-1.4-bin-zip=02edf3a0b994ba16627ac450ccfa15abeaad174b77b10db75a80dfd322daa68eb22b54b065a9533def87f9b99e82da42bbf0b5503e011bdad7e40c5dc3048c42 > > commons-release-plugin-1.4-javadoc-javadoc=d94901d528929edf00e71e235e7ac4fffcef9bc42a1b509fbbd8b672112b2793b70a617bb535bc07df075fd4cc0e652840d1b8e449dbe5727c967665197810d2 > > commons-release-plugin-1.4-test-sources-java-source=a05218b4aa30a18bd596af6ceb00587661da4ca81c93891e58ea697f0b5baff6c749cfd9ea3a93fe2a49bf434d64791cac71f87a589ed44236139b169425d89b > > commons-release-plugin-1.4-sources-java-source=2f60c9849ddba3750ee65773e2b67d15a0aef41b68be72959772f8263eb64ce7ed5c53f7b300c74c8208392b6f6f187c9aea027999a317eddcf3b0ba74364104 > > commons-release-plugin-1.4-tests-test-jar=b316749f21d8ba2f892602084f2b6b7166cd1de69fb498298c696cfeed71c82aed48ad375a9eda1492006275f875e8b5c85801c9f31d9d5575b2712c27d19a1e > > > > I have tested this with ***'mvn clean install site'*** using: > Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; > 2018-06-17T14:33:14-04:00) > Maven home: /usr/local/Cellar/maven/3.5.4/libexec > Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: >
Re: [ALL] SHA256/512 hashes
On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote: On 25 August 2018 at 09:48, Stefan Bodewig wrote: On 2018-08-25, Gary Gregory wrote: Our release plugin already creates SHA256 and SHA512 files and saves those to Apache's dev/dist for an RC as part of creating an RC, pushing it to Nexus and dist/dev. Ah, I've not looked at that yet. Is what you are referring to for a different purpose? Probably for those who don't want to use the release plugin :-) I was mainly following up on the thread about updating CP to AP 21 [1] But yes, it could be used as an alternative hashing method. I thought that the release plugin was intended for all components to converge on the same release "recipe"... In which case, if it is going to be put in CP rather than individual POMs, it should be in its own profile. (Or possibly two, one for SHA256 and one for SHA512?) +1 for *one* profile that leaves no room for working around global policy (thus simplifying release review work). Couldn't CP use a "property" from AP to ensure that the required hash is generated or the build will fail? Gilles [1] https://lists.apache.org/thread.html/a130864e39cc4ffb15c4018dc05142a405861b523fd14573010ea3e0@%3Cdev.commons.apache.org%3E - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [ALL] SHA256/512 hashes
On 25 August 2018 at 09:48, Stefan Bodewig wrote: > On 2018-08-25, Gary Gregory wrote: > >> Our release plugin already creates SHA256 and SHA512 files and saves those >> to Apache's dev/dist for an RC as part of creating an RC, pushing it to >> Nexus and dist/dev. Ah, I've not looked at that yet. >> Is what you are referring to for a different purpose? > > Probably for those who don't want to use the release plugin :-) I was mainly following up on the thread about updating CP to AP 21 [1] But yes, it could be used as an alternative hashing method. In which case, if it is going to be put in CP rather than individual POMs, it should be in its own profile. (Or possibly two, one for SHA256 and one for SHA512?) [1] https://lists.apache.org/thread.html/a130864e39cc4ffb15c4018dc05142a405861b523fd14573010ea3e0@%3Cdev.commons.apache.org%3E - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[imaging] Almost ready for a 1.0 alpha vote
Hi, All issues for 1.0 are now fixed. Thanks for the reviews/comments and for putting up with my messages about debug & other pending issues for a 1.0 release (: It was suggested to cut a 1.0-alpha prior to a full 1.0 release, and I have no objection for that. So I've created a local branch `release`, started reading the documentation for preparing a release and also for the new commons release plugin (looks great so far!!!). As I am almost running out of time before starting a new project at work$, I will try to call the vote in the next days. Otherwise, I will try again in a couple of months. Cheers Bruno - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [ALL] SHA256/512 hashes
On 2018-08-25, Gary Gregory wrote: > Our release plugin already creates SHA256 and SHA512 files and saves those > to Apache's dev/dist for an RC as part of creating an RC, pushing it to > Nexus and dist/dev. > Is what you are referring to for a different purpose? Probably for those who don't want to use the release plugin :-) Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-imaging pull request #35: IMAGING-154 Removed Debug class
Github user asfgit closed the pull request at: https://github.com/apache/commons-imaging/pull/35 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
