You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tooling.apache.org by "slawekjaranowski (via GitHub)" <gi...@apache.org> on 2026/06/05 18:04:51 UTC
[PR] Add `release-start` mojo [tooling-atr-maven-plugin]
slawekjaranowski opened a new pull request, #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45
- Introduced the `release-start` mojo to create a draft release in ATR if it does not exist.
- Updated documentation and site navigation for the new mojo.
- Added unit tests and integration tests for `release-start` functionality.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640262037
> given normal users do not yet have habits on reviewing project definition in ATR, automating the release start at ATR level seems too early to me
>
it will only create a release version in ART
> users need to learn, not use blindly
>
> let's do a first release integrated in ASF parent POM before trying to automate more: I hate automating things before manual experience = from experience, a recipe for complaints when the magic does not bring expected result
agree here, we can prepare configuration in ASF parent, but should be in disabled by default (or in dryRun)
so I see a three goal for integration:
- start-release - create a version
- upload - upload project release artifacts ... but it can be tricky, like project need provide a files list to upload
- upload-sboms - upload sbom artifact to art ( new goal - #44 )
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4694627610
if you really want to look at the future, when we automate everything, in the future, it will be done in GHA, not with a new Maven goal
less code to maintain
definitively, no hurry to add more code to maintain
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4701565247
suppressed by #54
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640234690
given normal users do not yet have habits on reviewing project definition in ATR, automating the release start at ATR level seems too early to me
users need to learn, not use blindly
let's do a first release integrated in ASF parent POM before trying to automate more: I hate automating things before manual experience = from experience, a recipe for complaints when the magic does not bring expected result
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4642839656
thinking at it and reviewing how I let the `pom.xml`: it forces `maven-atr-plugin` project key https://github.com/apache/tooling-atr-maven-plugin/blob/main/pom.xml#L506
I forgot that!
as Maven PMC members, we have https://release-test.apache.org/projects/maven-atr-plugin as a playgound
just change version in you local disk, and that's it
I just tried with `1.0.0-alpha-1-SNAPSHOT` in `pom.xml`, in the UI I did "Start a new release"
then `mvn clean install && mvn -Papache-release,push-to-atr clean deploy`
and boom: https://release-test.apache.org/compose/maven-atr-plugin/1.0.0-alpha-1-SNAPSHOT
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640346469
can we postpone adding more complexity please?
I wrote one month ago the plan for `push-to-atr` profile to give needed flexibility: and I'm fighting to just do a release
can we finish first the first step?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski closed pull request #45: Add `release-start` mojo
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640258946
do what yuo want, I'm tired not being able to do a release but continuing complexifying
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640245821
> "release flow" is really vague `mvn release:prepare release:perform` is not vague: do you expect other approaches?
yes projects can do release without release plugin, like:
https://logging.apache.org/logging-parent/release-instructions-project.html
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4642457308
> can we postpone adding more complexity please? I wrote one month ago the plan for `push-to-atr` profile to give needed flexibility: and I'm fighting to just do a release
>
> can we finish first the first step?
I hope not complexity I'm tring to find a way to be simple as possible when we add profile to ASF parent ...
connected issue:
- #48
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4694438346
> I know you have good intents I prefer forcing people to review their project configuration in ATR UI and click on "start release" than the magic where they discover after the fact ATR config
>
> we need to find the right training path, "to be simple as possible" but avoid the "to be magic" then have people ask about what happened behind the scene
It will be not magic, only version for release will be created, user still need to start a next step - voting manually after review release candidate in ATR.
With only `upload` goal, we need
- manually create version in ATR
- release project with push to ATR
- start voting in ATR
so one first step can be avoided
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4642776923
I know you have good intents
I prefer forcing people to review their project configuration in ATR UI and click on "start release"
than the magic where they discover after the fact ATR config
we need to find the right training path, "to be simple as possible" but avoid the "to be magic" then have people ask about what happened behind the scene
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4637776935
notice: for now, key step is ATR project creation, from `.asf.yaml`: perhaps we could display if `.asf.yaml` definition is done
and I think the key missing configuration is the vote templates, that is not available in `.asf.yaml` (and is too chatty IMHO to get added there)
the more we add in the Maven plugin, the more we should already test in real life what we have
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4638054700
> > create a draft release in ATR if it does not exist
>
> "if it does not exist" means that this new goal IMHO should be in fact merged with `check-composing`
>
> should we keep `release-start` as target or `check-composing` (or `start-release`), I don't have firm opinion yet
>
> I'm trying to guess how this will be integrated
>
> * in real global process: https://maven.apache.org/developers/release/maven-project-release-procedure.html
> * and in parent POM: https://maven.apache.org/pom/asf/
>
> we do `mvn release:prepare` = where we define the target version number is done followed by `mvn release:perform` with future `-Ppush-to-atr` profile: ok, that profile will check or create the version in ATR
>
> seems ok: just 2 goals is too much, one only seems sufficient
yes two goals for the sam can be too much ...
I would like to have release process simple as possible, I will prepare proposition for integration in next steps
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4638042646
> notice: for now, key step is ATR project creation, from `.asf.yaml`: perhaps we could display if `.asf.yaml` definition is done
>
> and I think the key missing configuration is the vote templates, that is not available in `.asf.yaml` (and is too chatty IMHO to get added there)
>
> the more we add in the Maven plugin, the more we should already test in real life what we have
It is each PMC responsibilite how to configure ATR, can be done be asf.yaml or by web gui, I would like to not introduce such configuration goals, like for templates and so on.
Plugin should be used during release proces, as you wrote the more in plugin more in test
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4637766371
> create a draft release in ATR if it does not exist
"if it does not exist" means that this new goal IMHO should be in fact merged with `check-composing`
should we keep `release-start` as target or `check-composing` (or `start-release`), I don't have firm opinion yet
I'm trying to guess how this will be integrated
- in real global process: https://maven.apache.org/developers/release/maven-project-release-procedure.html
- and in parent POM: https://maven.apache.org/pom/asf/
we do `mvn release:prepare` = where we define the target version number is done
followed by `mvn release:perform` with future `-Dpush-to-atr` profile: ok, that profile will check or create the version in ATR
seems ok: just 2 goals is too much, one only seems sufficient
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4638123424
> should we keep release-start as target or check-composing (or start-release), I don't have firm opinion yet
I would like to have only `release-start` in release flow, it will be one less manual step, even we want to manually re-deploy during release that goal will not create version again in atr
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `release-start` mojo [tooling-atr-maven-plugin]
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on PR #45:
URL: https://github.com/apache/tooling-atr-maven-plugin/pull/45#issuecomment-4640224493
"release flow" is really vague
`mvn release:prepare release:perform` is not vague: do you expect other approaches?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org