[
https://issues.apache.org/jira/browse/JAMES-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294329#comment-17294329
]
Benoit Tellier commented on JAMES-3510:
---------------------------------------
I am unsure as the commiter can hardly guaranty the builder and thus the
artifact had not been compromised - as it is a remote machine...
I did took some time to see if some other Apache projects had automated their
release, and sampled ~15 projects listed there https://ci-builds.apache.org/
(spark, activeMQ, kafka etc...)
The only automated step is deploying snapshots, which we already have automated.
> Automate release procedure to speed up releases
> -----------------------------------------------
>
> Key: JAMES-3510
> URL: https://issues.apache.org/jira/browse/JAMES-3510
> Project: James Server
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
>
> Could we collect here the steps that could be automated to fasten the process
> of creating a new release.
> Me (or my colleague Andreas) would be willing to work on some of the
> automation tasks.
> I propose automating publishing to Maven Central (building artifacts and PGP
> signing them)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
