[GitHub] [incubator-pekko] spangaer commented on issue #130: Setup the release process

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

spangaer commented on issue #130:
URL: https://github.com/apache/incubator-pekko/issues/130#issuecomment-1421339657

   Well this a word storm if you have to pick it up. (I tried to consider all of the above statements, so apologies if I stupidly missed out on something with following reply).
   
   Just want to throw something on to the table, what if:
   
   1. A tag in Git(Hub) instead of triggering a binary release workflow builds the zip which is considered "the release" by the ASF.
   2. In the process of constructing that zip 1 file, not in Git, is added to the archive, which holds all Git version info
     - Git commit sha
     - Git version as defined from tag
   3. The SBT build is aware that, if above file is defined, all version info is coming from that file and not from Git (the Zip has no Git context)
   4. Now you have the artifact on which the "validation" and "voting" should take place.
   5. Once the zip is voted to release and published on the "official location" some automation pipeline picks up that zip from that very place and builds and publishes the Maven Central artifacts from it.
   
   I know it doesn't naturally fall in to the SBT plugin ecosystem, but I can't help at feel as this being how the authors of the Apache process envisioned it?
   
   Clearly you should be damn sure about the release before setting the tag, because mutating tags seems really not done. So `4` above should be somewhat of a formality. It's `5` the publishing from the zip, where "the difference" sits from proposed strategies sits, I think.


-- 
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