I don’t know enough about how Maven works to say whether it’s a blocker in 
practice. I’m alright with semantic versioning here in theory at least!

> On Sep 5, 2023, at 11:50 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
> 
> I want to switch to semantic versioning to make it clear what is a bug fix,
> what introduces new features, etc. I plan to make bug fix releases more
> often to smoothen the release process of parented projects. Though I see
> your point regarding `9 > 1.10.0`. If you think this is a blocker and we
> should rather go with `9.1.0`, etc. instead, please let me know.
> 
> On Tue, Sep 5, 2023 at 6:45 PM Matt Sicker <m...@musigma.org> wrote:
> 
>> This doesn’t exactly match the versioning scheme for logging-parent which
>> was a simple integer. This version number is considered much lower than the
>> latest release by Maven as a result.
>> 
>>> On Sep 4, 2023, at 2:33 PM, Volkan Yazıcı <vol...@yazi.ci> wrote:
>>> 
>>> This is a vote to release the Apache Logging Parent 1.10.0.
>>> 
>>> Source repository: https://github.com/apache/logging-parent
>>> Commit: 3dd83461faa058690a5ed821ee81dfc2d744ec7c
>>> Distribution: https://dist.apache.org/repos/dist/dev/logging
>>> Nexus:
>> https://repository.apache.org/content/repositories/orgapachelogging-1113
>>> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
>>> 
>>> Please download, test, and cast your votes on this mailing list.
>>> 
>>> [ ] +1, release the artifacts
>>> [ ] -1, don't release, because...
>>> 
>>> This vote is open for 72 hours and will pass unless getting a
>>> net negative vote count. All votes are welcome and we encourage
>>> everyone to test the release, but only the Logging Services PMC
>>> votes are officially counted. At least 3 +1 votes and more
>>> positive than negative votes are required.
>>> 
>>> # Release Notes
>>> 
>>> This minor release contains various improvements that we expect to
>>> relieve the load on `pom.xml` and GitHub Actions workflows of
>>> Maven-based projects we parent. This is of particular importance while
>>> managing and cutting releases from multiple repositories.
>>> See `README.adoc` for the complete list of features and their usage.
>>> 
>>> See [this `logging-log4j-tools` GitHub Actions workflow
>>> run](
>> https://github.com/apache/logging-log4j-tools/actions/runs/6070379396)
>>> demonstrating a successful release cut using a SNAPSHOT version of
>>> this `logging-parent` release. All preparations (release notes,
>>> distribution ZIP, vote & announcement emails, etc.) are staged to both
>>> Nexus and SVN and waiting the release manager to proceed. As a matter
>>> of fact, this very release of `logging-parent` is cut by the very same
>>> reusables too.
>>> 
>>> ## Changes
>>> 
>>> ### Added
>>> 
>>> * Added `changelog-export` profile to easily export changelogs to
>> Markdown files
>>> * Added `changelog-release` profile to easily move
>>> `src/changelog/.?.x.x` contents to their associated release directory
>>> * Added `deploy` profile to ease the Maven `deploy` goal
>>> * Added `distribution` profile to easily create a distribution file
>>> containing Git-tracked sources, release notes, binary attachments,
>>> `NOTICE.txt`, etc.
>>> * Documented release instructions (i.e., `RELEASING.md`)
>>> * Added `release` profile to share common release-specific Maven
>> configuration
>>> * Added reusable GitHub Actions workflows to share CI boilerplate for
>>> other repositories
>>> * Switched to using `log4j-changelog-maven-plugin` for managing
>>> changelog and release notes
>> 
>> 

Reply via email to