Skip to content

Conversation

@marko-bekhta
Copy link
Member

Hey Davide 🙂 👋🏻
I'm opening this as a draft for now. We'll need to merge the scripts update first.

the idea behind this iteration of release updates is .... project builds should only build the artifacts (e.g. jars/javadocs/html docs etc) and put them in the specific location. Then the release scripts would do the rest.
This means that the project build does not need to do any git operations or deployments or ... 😃

)

// See https://docs.asciidoctor.org/gradle-plugin/latest/common-task-configuration/#choosing-an-execution-mode-for-asciidoctorj
executionMode = org.ysb33r.grolifant.api.core.jvm.ExecutionMode.JAVA_EXEC
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one is a bonus 😄
we don't really need it for releases or anything ... but it helps with asciidoc building 🙂

@DavideD
Copy link
Member

DavideD commented Nov 7, 2025

Nice, thanks.

@DavideD DavideD changed the title Simplify the release process [4.2] Simplify the release process Nov 12, 2025
@DavideD DavideD added the 4.2 label Nov 12, 2025
Comment on lines +1 to +3

* See the [website](https://hibernate.org/reactive/releases/{{releaseVersionFamily}}) for requirements and compatibilities.
* See the [What's New](https://hibernate.org/reactive/releases/{{releaseVersionFamily}}/#whats-new) guide for details about new features and capabilities.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea is that each project/branch can add something extra about a particular release if it wants to.
This template is then included in the reactive template https://github.com/hibernate/hibernate-release-scripts/blob/b5852b88067e9b71fd746a69917a2b92576ce7f1/jreleaser/github-release-note-template/reactive.tpl

but if you'd want something different for your github releases we can discuss that 🙂

@marko-bekhta marko-bekhta marked this pull request as ready for review November 13, 2025 14:52
@marko-bekhta
Copy link
Member Author

Hey @DavideD 👋🏻 🙂

sooooo the release scripts are merged and we can merge these build updates as well,
let me know if you'd want to have a look at it + backports or if I should merge them all 🙂
(but we should definety merge the updates before we try the next Reactive release)

@DavideD
Copy link
Member

DavideD commented Nov 13, 2025

Thanks @marko-bekhta,
I gave them a quick look and they seem fine to me.

I will merge them tomorrow morning, if that's ok

@DavideD DavideD linked an issue Nov 13, 2025 that may be closed by this pull request
@DavideD
Copy link
Member

DavideD commented Nov 13, 2025

I created an issue to group the PRs in one place, but there's no need to update the commits

@marko-bekhta
Copy link
Member Author

ok, thanks! 🙂

I will merge them tomorrow morning, if that's ok

yes, as long as you merge them before doing a release we should be fine 🙂

@DavideD DavideD added build Something related to the build ci Changes to the Jenkins pipeline or GitHub workflows labels Nov 14, 2025
@DavideD DavideD merged commit 2d70d6f into hibernate:main Nov 14, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4.2 build Something related to the build ci Changes to the Jenkins pipeline or GitHub workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Simplify the release process

2 participants