Thank you for your thoughtful explanation. I'm 100% ok with calling the RC 1.0-alpha4 (alpha3 is was 2 years ago). I'll re-roll the RC in the morning.
Gary On Tue, Mar 26, 2024, 6:07 PM Bruno Kinoshita <brunodepau...@gmail.com> wrote: > Hi Gary, > > The M name is something Maven uses a lot and (to me) suggests something > > users might be more willing to try than anything labeled alpha or beta. > > YMMV of course. > > > Now that you mention it, I do remember installing some Maven versions that > had the M in its version! > > From a compatibility POV, anything can happen until 1.0, so the only name > > that matters is 1.0. We have no guidelines except what the world does at > > large with alpha, beta, or milestone, plus I would not restrict > outlrselves > > saying we can't do this or that because we are in beta and not alpha > > anymore. The basic goal IMO is to up the usage and make sure we have a > nice > > API for 1.0. > > > I think users are already trying the -alpha release, and I think it'd be > better to use alpha3: > > - Less surprise to users, as alpha1 -> alpha2 -> alpha3 is intuitive > - Not all users may be familiar with M1, M2 (although that could be just > me) > - I searched milestone release maven, and found this SO as the very first > hit > > https://stackoverflow.com/questions/3687208/what-does-m1-mean-in-a-maven-repository > > >A milestone means that the application got a huge improvement from the > todo list. A release candidate is a release that can be the final release > unless some major bugs are found. > > I do not think we had a huge improvement, yet, as there are old issues from > the first 1.0 vote that were not fixed yet, and other bugs reported by > users of the alpha1/2 releases that would be nice to fix before it's ready > to be released. > > I think what we have in Imaging right now matches more the alpha release > described in ASF's release policy page > https://www.apache.org/legal/release-policy.html#release-types, > > > Releases that only represent a project milestone and are intended only > for bleeding-edge developers working outside the project are called > "alpha". > > as I think Imaging's API still needs some trimming and may change in > this/next releases, so more like a bleeding-edge, which should be clear to > users getting an alpha3 release. > > From my point of view we do not really need to increase the number of users > testing the releases, but work through the issues reported (mea culpa, > sorry), and fix the 1.x issues. Once that's done, I think we could have an > M1 release then, and promote it more to get more users before the 1.0 final > (if needed, or straight to 1.0). > > Wouldn't you consider an alpha3 instead, to avoid any issues to users, and > an M1 when we are closer to 1.0 (quite sure an alpha4 or M2 will be > needed... maybe more...). > > Bruno > > On Mon, 25 Mar 2024 at 16:24, Gary Gregory <garydgreg...@gmail.com> wrote: > > > Hi Bruno, > > > > The M name is something Maven uses a lot and (to me) suggests something > > users might be more willing to try than anything labeled alpha or beta. > > YMMV of course. > > > > From a compatibility POV, anything can happen until 1.0, so the only name > > that matters is 1.0. We have no guidelines except what the world does at > > large with alpha, beta, or milestone, plus I would not restrict > outlrselves > > saying we can't do this or that because we are in beta and not alpha > > anymore. The basic goal IMO is to up the usage and make sure we have a > nice > > API for 1.0. > > > > HTH, > > Gary > > > > > > On Mon, Mar 25, 2024, 10:49 AM Bruno Kinoshita <brunodepau...@gmail.com> > > wrote: > > > > > Will try the branch and vote later this week. > > > > > > From another thread, I think M1 will behave exatcly like an alpha > release > > > would. > > > > > > I am more used to alpha/beta/then final release process. > > > > > > Could you clarify how the M1 will distinguish from an alpha or 1.0 > > release? > > > > > > Tha ks for preparing the release! > > > > > > Bruno > > > > > > On Mon, 25 Mar 2024, 14:17 Gary Gregory, <ggreg...@apache.org> wrote: > > > > > > > We have fixed a few bugs and added some enhancements since Apache > > > > Commons Imaging 1.0-alpha3 was released, so I would like to release > > > > Apache Commons Imaging 1.0.0-M1. > > > > > > > > Apache Commons Imaging 1.0.0-M1 RC1 is available for review here: > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1 > > > > (svn revision 68122) > > > > > > > > The Git tag commons-imaging-1.0.0-M1-RC1 commit for this RC is > > > > 53565f604393f5f3e09b87be020567d201905a44 which you can browse here: > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=53565f604393f5f3e09b87be020567d201905a44 > > > > You may checkout this tag using: > > > > git clone > https://gitbox.apache.org/repos/asf/commons-imaging.git > > > > --branch < > > > https://gitbox.apache.org/repos/asf/commons-imaging.git--branch> > > > > commons-imaging-1.0.0-M1-RC1 commons-imaging-1.0.0-M1-RC1 > > > > > > > > Maven artifacts are here: > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1707/org/apache/commons/commons-imaging/1.0.0-M1/ > > > > > > > > These are the artifacts and their hashes: > > > > > > > > #Release SHA-512s > > > > #Mon Mar 25 12:37:27 UTC 2024 > > > > > > > > > > > > > > org.apache.commons_commons-imaging-1.0.0-M1.spdx.json=87c9326b12ddb92d53483141f825fad966c432405120f1296f70a6dba54f7ca87f80af26ce209bcca8bdd89b4e93ac464cd8546d19919858504d6a20d2f211cc > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-sources.jar=5e0d15188af8b7278766d8efe2d3fa08809f782f7db580dd8115bcd8dd66de0534599722050c03d0e8347980b398c68f2eea938021a30d8d44b751c5175fdfb8 > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-bom.json=12a3e4c949580680b8bed4be2a5836cf2ed4d0235516b94b8d566c574176429ba7297a253f990f7515040b2ed978389eecc762f5166f6827619bb5494da0f625 > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-src.zip=f4bf0919f2708eda8ab24cf92637dbf5e7ff443741911add2c7375c1161d798244ff1ef7bea47bdfddb9b1e2b8f65b5a212679729c4e22f9aad8815a1ebe2f0b > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-test-sources.jar=96ea44d7b42c9dd01e3250d4854506fde6876ff76e8a55a2e76e5df9d0a24bb7302d4288c05e284c3d122ebc61fb0ddd34741b97f60fec86b9141019c10c449b > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-bin.tar.gz=1f7618ef5dfc7a6841aafb79f901d0c2010fa066ffccb5a4ff4c3e3083c0214bb4e998878ef3ca44c27a8df4a4e39888b7606e8c1f6d522c3029ccf4a9ec626e > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-bom.xml=027ef7700828133cf25d8f0ac01dffe2266c8a635cde7bbfaa421faf84af0f0adb4389e48b62b3955105fb99befd0a62e31b0ecdddfeb611b0662612eb9dc6fa > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-src.tar.gz=f0f1c814993883c2913d258d50eb83877ea65f961e2a8aec06de1877e394de34eafdeed0f39ee67bd710da5e4efc8e8adb1d52e87ecb100c74a1343fa1fe09bc > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-tests.jar=f07ddff5273d32299261e51673f0a1030075ff72293f22087cc732e227b762c83dbad2cd59ed47c7409528bb9fe1fd4833a13e45163a357244487b002700dc8b > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-javadoc.jar=91b5998ff11bcd76af6346ea37f8fbb14c6390b02b48e9e4ee7b4e6c31b8b7344227e7c2fea6894cd866a3330a0c30a57ff1007a61549e07642312e3d2f2ae6f > > > > > > > > > > > > > > commons-imaging-1.0.0-M1-bin.zip=bf431713086e2fc61a9eb52eed1fd9043ca6c36601c81c3f775c110795e0d9dbdca09a768785ce4137cc9b822f9a736a50c2b8758ec58a2caa14695f68538784 > > > > > > > > I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P > > > > jacoco -P japicmp clean package site deploy' using: > > > > > > > > openjdk version "17.0.10" 2024-01-16 > > > > OpenJDK Runtime Environment Homebrew (build 17.0.10+0) > > > > OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, > > sharing) > > > > > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > > > Maven home: /usr/local/Cellar/maven/3.9.6/libexec > > > > Java version: 17.0.10, vendor: Homebrew, runtime: > > > > /usr/local/Cellar/openjdk@17 > /17.0.10/libexec/openjdk.jdk/Contents/Home > > > > Default locale: en_US, platform encoding: UTF-8 > > > > OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac" > > > > > > > > Darwin **** 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 > > > > PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64 > > > > > > > > Details of changes since 1.0-alpha3 are in the release notes: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1/RELEASE-NOTES.txt > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1/site/changes-report.html > > > > > > > > This release does not preserve binary compatibility with previous > alpha > > > > releaes. > > > > > > > > Site: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1/site/index.html > > > > (note some *relative* links are broken and the 1.0.0-M1 > > > > directories are not yet created - these will be OK once the site is > > > > deployed.) > > > > > > > > RAT Report: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1/site/rat-report.html > > > > > > > > KEYS: > > > > https://downloads.apache.org/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, > > > > > > > > Gary Gregory, > > > > Release Manager (using key 86fdc7e2a11262cb) > > > > > > > > For 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. > > > > > > > > 1a) Clone and checkout the RC tag > > > > > > > > git clone https://gitbox.apache.org/repos/asf/commons-imaging.git > > > > --branch < > > > https://gitbox.apache.org/repos/asf/commons-imaging.git--branch> > > > > commons-imaging-1.0.0-M1-RC1 commons-imaging-1.0.0-M1-RC1 > > > > cd commons-imaging-1.0.0-M1-RC1 > > > > > > > > 1b) Download and unpack the source archive from: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-M1-RC1/source > > > > > > > > 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 -V clean package > > > > > > > > You can record the Maven and Java version produced by -V in your VOTE > > > > reply. > > > > To gather OS information from a command line: > > > > Windows: ver > > > > Linux: uname -a > > > > > > > > 5) Build the site for a single module project > > > > > > > > Note: Some plugins require the components to be installed instead of > > > > packaged. > > > > > > > > mvn site > > > > Check the site reports in: > > > > - Windows: target\site\index.html > > > > - Linux: target/site/index.html > > > > > > > > Note that the project reports are created for each module. > > > > Modules can be accessed using the 'Project Modules' link under > > > > the 'Project Information' menu (see <path-to-site>/modules.html). > > > > > > > > -the end- > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > >
