[GitHub] [incubator-pekko] jrudolph commented on issue #85: Automate the release

["jrudolph (via GitHub)" <gi...@apache.org>]

jrudolph commented on issue #85:
URL: https://github.com/apache/incubator-pekko/issues/85#issuecomment-1404889771

   > * we don't use Sonatype
   
   Maybe we should clarify what a release is and what the desired outcome of doing a release is. How do artifacts end up on Maven Central if not going through Sonatype? Let's start listing all the steps necessary to do different kinds of releases (snapshots, RCs, and GA) and only then start about automating any of it. I imagine this is at least partly about what Apache considers a release? If yes, then we should clarify what it entails.
   
   I would consider `sbt-ci-release` to be a tool to work with sonatype. If we don't go through sonatype (or a process very similar to sonatype with staging repos etc), we probably should not use it. Afaik, the main reason it was created was that sonatype (Nexus) needs some manual handholding to finally publish something to Maven Central.
   
   AFAIK sbt-release is a plugin to organize a release-process that has multiple steps but is more abstract than publishing to a repository.
   
   If this is just about pushing artifacts to a maven-compatible repository, we might not need any plugins for just that.


-- 
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: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org