Re: [imaging] Preparing vote for imaging-1-0-alpha3 (last alpha release)
Nice job, Bruno! Thanks for pushing this. Matt On Wed, May 11, 2022, 11:32 PM Bruno Kinoshita wrote: > Hi, > > We have fixed all the issues that were raised as blockers for 1.0 some > years ago (4? maybe 5 years ago?). I'm finishing the preparations for the > 1.0-alpha3 vote for Imaging. It's the last alpha release I have planned. > > I started working on Imaging when I became curious if we could use it as an > IIIF processor in Cantaloupe [1]. I never had time to try that, and instead > ended up spending a long time working on these issues for the 1.0 release. > Hoping now to use the alpha3 release with IIIF, fix any bugs I may find, > give users 6-12 months to send their feedback, and then cut 1.0 if there > are no blockers. > > I received feedback from users of Imaging that were able to use > alpha1/alpha2 in their Android apps, GIS solutions, simple web apps, and > even in visual arts with processing.org. Having the 1.0 in Maven should > allow a few more users/devs to use it. > > Cheers > Bruno > > [1] https://cantaloupe-project.github.io/manual/3.1/processors.html >
Re: [imaging] Preparing vote for imaging-1-0-alpha3 (last alpha release)
My primary interest for Commons Imaging is using it to access geo-referenced TIFF file (GeoTIFF) . So far, it's worked out pretty well. The TIFF file format provides a flexible definition for attaching metadata to images. Back in the 1990's, the Geographic Information System (GIS) community started using a specification that allowed TIFF files to be overlaid on map displays. Nowadays, GeoTIFFs are supported by all the major GIS systems. While Imaging is useful for things like aerial photographs and satellite images, it also has the capability to carry numerical information. And there are some excellent, high-resolution elevation data sources available in TIFF format. I've been using the Commons Imaging API to access elevation grids with a 10-meter spacing from the U.S. Geological Survey (USGS), global elevation data sets from NASA's Shuttle Radar Topography Mission (SRTM) that has a 30-meter spacing, some European and Japanese sources, and high-resolution bathymetry products. Not all TIFF API's support access to that kind of data, but Commons Imaging does. And, personally, I think that Imaging is one of the easier-to-use libraries for accessing numerical data from TIFFs. Anyway, I am looking forward to seeing the alpha-3 release be available via the Maven Central Repository. Bruno has introduced some significant improvements to the API. Having them available via Maven will be a boon to the Java developer community. Thanks, Gary (the other Gary) On Thu, May 12, 2022 at 12:32 AM Bruno Kinoshita wrote: > Hi, > > We have fixed all the issues that were raised as blockers for 1.0 some > years ago (4? maybe 5 years ago?). I'm finishing the preparations for the > 1.0-alpha3 vote for Imaging. It's the last alpha release I have planned. > > I started working on Imaging when I became curious if we could use it as an > IIIF processor in Cantaloupe [1]. I never had time to try that, and instead > ended up spending a long time working on these issues for the 1.0 release. > Hoping now to use the alpha3 release with IIIF, fix any bugs I may find, > give users 6-12 months to send their feedback, and then cut 1.0 if there > are no blockers. > > I received feedback from users of Imaging that were able to use > alpha1/alpha2 in their Android apps, GIS solutions, simple web apps, and > even in visual arts with processing.org. Having the 1.0 in Maven should > allow a few more users/devs to use it. > > Cheers > Bruno > > [1] https://cantaloupe-project.github.io/manual/3.1/processors.html >
[VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC1
We have fixed quite a few bugs and added some significant enhancements since Apache Commons Imaging 1.0-alpha2 was released, so I would like to release Apache Commons Imaging 1.0-alpha3. Apache Commons Imaging 1.0-alpha3 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1 (svn revision 54478) The Git tag commons-imaging-1.0-alpha3-RC1 commit for this RC is b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-imaging.git --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1586/org/apache/commons/commons-imaging/1.0-alpha3/ These are the artifacts and their hashes: #Release SHA-512s #Fri May 13 16:54:49 NZST 2022 commons-imaging-1.0-alpha3-tests.jar=0435be91af272c3d9601d1e0ff5a2746ce24e67b39678a8185b566965eaa8fc84eb86da9bea86524f75552f543eca79624ac0cfd34e1b7d178420f12542c252a commons-imaging-1.0-alpha3-sources.jar=9f4218c8d66d2fec168571fe68b24e2770b7c61e91c024338f0a3a5409ca2fe0b558599116f194ee01d21994f99480a37c85427e43c8d9ed91c0acb8b3d49325 commons-imaging-1.0-alpha3-bin.zip=dbd064f46a4336d222ccb192ede94075e972360ad8b718fb2558466c462b74434b1f2afc0ec4cf251712070bc34a39770fd355d505ea63607a9f14d0a33b98fd commons-imaging-1.0-alpha3-src.zip=517a134f9e5df3ba99de70dcdea081be05d23d0eb25d45ce638b374c0728ad599a5834b97663e5564f80f839a76f62cc963746d75f7badc433de426a230aff0c commons-imaging-1.0-alpha3-javadoc.jar=8477e036b0e09e51d9c2af01b0a8a3519d58db14eb1d46f49c512fef23d4ea9f4fb2e89e5be3ead6aa70f128578464b74608b8b832215ca71df3e2dfbd0db357 commons-imaging-1.0-alpha3-test-sources.jar=2ec8b641a73ad45d9df8d6daef412baa25be8ec4c9dddea1daf033ff60eea88dfd959690adce0e74c97424a77bc9c5732ddbfe8862c39d437d750fc706d54ecc commons-imaging-1.0-alpha3-bin.tar.gz=3c4fcf1bc61cb771b125d4134c96997f6d82dd20f053d8d229cc20cb97904bd306967db57253cc062a609fae7a091c2be1ecb36cf9bb116d3bce032edec40590 commons-imaging-1.0-alpha3-src.tar.gz=065b69bd337e5609750fb396175e7872d8f2d62e1e0f76c3a443c371ccbe40be16078bd17551ed15b2c918efe1417f6159dbdf158a3d8638de6510405af357e6 I have tested this with ***'mvn clean install site'*** using: *** Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) Maven home: /opt/apache-maven-3.8.5 Java version: 11.0.15, vendor: Private Build, runtime: /usr/lib/jvm/java-11-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.0-110-generic", arch: "amd64", family: "unix" *** Details of changes since 1.0-alpha2 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/index.html (note some *relative* links are broken and the 1.0-alpha3 directories are not yet created - these will be OK once the site is deployed.) CLIRR and JApiCmp reports are not being used during the alpha releases, but will be used again in the 1.0 release (alpha3 is expected to be the last 1.0 alpha release.) There are some PMD and CPD issues that will be fixed before the 1.0 release. RAT Report: https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/rat-report.html KEYS: https://www.apache.org/dist/commons/KEYS Please review the release candidate and vote. This vote will close no sooner than 72 hours from now. [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release because... Thank you, Bruno P. Kinoshita, Release Manager (using key 33C6E01240C5468C2B7A556954E2764B48A42DF0) The following is intended as a helper and refresher for reviewers. Validating a release candidate == These guidelines are NOT complete. Requirements: Git, Java, Maven. You can validate a release from a release candidate (RC) tag as follows. 1) Clone and checkout the RC tag git clone https://gitbox.apache.org/repos/asf/commons-imaging.git --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1 cd commons-imaging-1.0-alpha3-RC1 2) Check Apache licenses This step is not required if the site includes a RAT report page which you then must check. mvn apache-rat:check 3) Check binary compatibility Older components still use Apache Clirr: This step is not required if the site includes a Clirr report page which you then must check. mvn clirr:check Newer components use JApiCmp with the japicmp Maven Profile: This step is not required if the site includes a JApiCmp report page which you then must check. mvn install -DskipTests -P japicmp japicmp:cmp 4) Build the package mvn
Re: [imaging] Preparing vote for imaging-1-0-alpha3 (last alpha release)
Thank you Matt! :) On Thu, 12 May 2022 at 22:16, Matt Benson wrote: > Nice job, Bruno! Thanks for pushing this. > > Matt > > On Wed, May 11, 2022, 11:32 PM Bruno Kinoshita > wrote: > > > Hi, > > > > We have fixed all the issues that were raised as blockers for 1.0 some > > years ago (4? maybe 5 years ago?). I'm finishing the preparations for the > > 1.0-alpha3 vote for Imaging. It's the last alpha release I have planned. > > > > I started working on Imaging when I became curious if we could use it as > an > > IIIF processor in Cantaloupe [1]. I never had time to try that, and > instead > > ended up spending a long time working on these issues for the 1.0 > release. > > Hoping now to use the alpha3 release with IIIF, fix any bugs I may find, > > give users 6-12 months to send their feedback, and then cut 1.0 if there > > are no blockers. > > > > I received feedback from users of Imaging that were able to use > > alpha1/alpha2 in their Android apps, GIS solutions, simple web apps, and > > even in visual arts with processing.org. Having the 1.0 in Maven should > > allow a few more users/devs to use it. > > > > Cheers > > Bruno > > > > [1] https://cantaloupe-project.github.io/manual/3.1/processors.html > > >
Re: [imaging] Preparing vote for imaging-1-0-alpha3 (last alpha release)
Thanks Gary! 1.0-alpha3 has a lot of changes (some important bug fixes) thanks to your work with the TIFF and other parsers. After some hiccups I managed to get a 1.0-alpha3 branch/tag that looks OK. I've started the RC1 VOTE thread for 1.0 alpha3. If all goes well it should be available in Maven Central in 5-10 days (I'll leave it open for a bit longer since it's almost weekend - already here in NZ). -Bruno On Thu, 12 May 2022 at 23:54, Gary Lucas wrote: > My primary interest for Commons Imaging is using it to access > geo-referenced TIFF file (GeoTIFF) . So far, it's worked out pretty well. > > The TIFF file format provides a flexible definition for attaching metadata > to images. Back in the 1990's, the Geographic Information System (GIS) > community started using a specification that allowed TIFF files to be > overlaid on map displays. Nowadays, GeoTIFFs are supported by all the major > GIS systems. > > While Imaging is useful for things like aerial photographs and satellite > images, it also has the capability to carry numerical information. And > there are some excellent, high-resolution elevation data sources available > in TIFF format. I've been using the Commons Imaging API to access > elevation grids with a 10-meter spacing from the U.S. Geological Survey > (USGS), global elevation data sets from NASA's Shuttle Radar Topography > Mission (SRTM) that has a 30-meter spacing, some European and Japanese > sources, and high-resolution bathymetry products. Not all TIFF API's > support access to that kind of data, but Commons Imaging does. And, > personally, I think that Imaging is one of the easier-to-use libraries for > accessing numerical data from TIFFs. > > Anyway, I am looking forward to seeing the alpha-3 release be available via > the Maven Central Repository. Bruno has introduced some significant > improvements to the API. Having them available via Maven will be a boon to > the Java developer community. > > Thanks, > > Gary (the other Gary) > > On Thu, May 12, 2022 at 12:32 AM Bruno Kinoshita > wrote: > > > Hi, > > > > We have fixed all the issues that were raised as blockers for 1.0 some > > years ago (4? maybe 5 years ago?). I'm finishing the preparations for the > > 1.0-alpha3 vote for Imaging. It's the last alpha release I have planned. > > > > I started working on Imaging when I became curious if we could use it as > an > > IIIF processor in Cantaloupe [1]. I never had time to try that, and > instead > > ended up spending a long time working on these issues for the 1.0 > release. > > Hoping now to use the alpha3 release with IIIF, fix any bugs I may find, > > give users 6-12 months to send their feedback, and then cut 1.0 if there > > are no blockers. > > > > I received feedback from users of Imaging that were able to use > > alpha1/alpha2 in their Android apps, GIS solutions, simple web apps, and > > even in visual arts with processing.org. Having the 1.0 in Maven should > > allow a few more users/devs to use it. > > > > Cheers > > Bruno > > > > [1] https://cantaloupe-project.github.io/manual/3.1/processors.html > > >
Re: [VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC1
My own vote [x] +1 Release these artifacts I had to downgrade Apache Commons Parent to 52 as I couldn't generate the site - the generated layout was old, as if it couldn't load the maven site plugin theme, and rat and jdepend both failed to run [1], but also had to override the Apache Commons Release Plugin due to errors when "detaching distribution" [2]. I left notes in the pom.xml file for the issues above, with links to the related JIRA issues. Checked signatures, manually inspected files from the dist area, closed the maven repo, reviewed the Maven generated site reports, confirmed NOTICE/LICENSE/RELEASE-NOTES.txt looked OK, and checked that JIRA/GitHub pull requests were updated correctly. For the next release I will try to: - close as many PMD/CPD issues as possible - increase coverage - fix a few bugs based on user feedback - remove these TODO's/notes from pom.xml and upgrade to commons-parent-53 Thanks! -Bruno [1] https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32 [2] https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32 On Fri, 13 May 2022 at 17:26, Bruno Kinoshita wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Imaging 1.0-alpha2 was released, so I would like to > release Apache Commons Imaging 1.0-alpha3. > > Apache Commons Imaging 1.0-alpha3 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1 > (svn revision 54478) > > The Git tag commons-imaging-1.0-alpha3-RC1 commit for this RC is > b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-imaging.git > --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1586/org/apache/commons/commons-imaging/1.0-alpha3/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri May 13 16:54:49 NZST 2022 > > commons-imaging-1.0-alpha3-tests.jar=0435be91af272c3d9601d1e0ff5a2746ce24e67b39678a8185b566965eaa8fc84eb86da9bea86524f75552f543eca79624ac0cfd34e1b7d178420f12542c252a > > commons-imaging-1.0-alpha3-sources.jar=9f4218c8d66d2fec168571fe68b24e2770b7c61e91c024338f0a3a5409ca2fe0b558599116f194ee01d21994f99480a37c85427e43c8d9ed91c0acb8b3d49325 > > commons-imaging-1.0-alpha3-bin.zip=dbd064f46a4336d222ccb192ede94075e972360ad8b718fb2558466c462b74434b1f2afc0ec4cf251712070bc34a39770fd355d505ea63607a9f14d0a33b98fd > > commons-imaging-1.0-alpha3-src.zip=517a134f9e5df3ba99de70dcdea081be05d23d0eb25d45ce638b374c0728ad599a5834b97663e5564f80f839a76f62cc963746d75f7badc433de426a230aff0c > > commons-imaging-1.0-alpha3-javadoc.jar=8477e036b0e09e51d9c2af01b0a8a3519d58db14eb1d46f49c512fef23d4ea9f4fb2e89e5be3ead6aa70f128578464b74608b8b832215ca71df3e2dfbd0db357 > > commons-imaging-1.0-alpha3-test-sources.jar=2ec8b641a73ad45d9df8d6daef412baa25be8ec4c9dddea1daf033ff60eea88dfd959690adce0e74c97424a77bc9c5732ddbfe8862c39d437d750fc706d54ecc > > commons-imaging-1.0-alpha3-bin.tar.gz=3c4fcf1bc61cb771b125d4134c96997f6d82dd20f053d8d229cc20cb97904bd306967db57253cc062a609fae7a091c2be1ecb36cf9bb116d3bce032edec40590 > > commons-imaging-1.0-alpha3-src.tar.gz=065b69bd337e5609750fb396175e7872d8f2d62e1e0f76c3a443c371ccbe40be16078bd17551ed15b2c918efe1417f6159dbdf158a3d8638de6510405af357e6 > > > > I have tested this with ***'mvn clean install site'*** using: > *** > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) > Maven home: /opt/apache-maven-3.8.5 > Java version: 11.0.15, vendor: Private Build, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-110-generic", arch: "amd64", family: > "unix" > *** > > Details of changes since 1.0-alpha2 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/index.html > (note some *relative* links are broken and the 1.0-alpha3 directories > are not yet created - these will be OK once the site is deployed.) > > CLIRR and JApiCmp reports are not being used during the alpha releases, > but will be used again in the > 1.0 release (alpha3 is expected to be the last 1.0 alpha release.) > > There are some PMD and CPD issues that will be fixed before the 1.0 > release. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/rat-report.html > > KEYS: > https://www.apache.org/dist/commons/KEYS > > Please review the rele
