I think simplifying the process makes sense and adding a reminder in the review email to clear the cache should address the concern.
On Mon, 24 Feb 2025 at 03:15, kerr <hepin1...@gmail.com> wrote: > IIRC, akka's release process is quite simple, so does the scala/scala3 > itself which will just be released with CI, and then later announce it . > 何品 > > > PJ Fanning <fannin...@apache.org> 于2025年2月24日周一 04:25写道： > >> Hi, >> Apache Pekko is the only project that I am aware of that produces RC >> jars (jars with RC in the version numbering) and then creates a 2nd >> set of jars after the release vote passes. Most projects create jars >> that have the prospective release number and just release them when >> the vote passes. This takes up extra release manager effort, extra >> review effort and leads to a longer release cycle. >> The jars are left in the repository.apache.org staging area as opposed >> to being released. >> The only benefit as far as I can see of having the 2 stage jar build >> is that people reviewing the jars might forget to clear the caches on >> their machines. I still don't think this is worth the extra release >> complication at this point. >> >> Does anyone have any opinions on this? I would like to try out the >> change to the process in the upcoming pekko-projection release. >> >> Thanks, >> PJ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> For additional commands, e-mail: dev-h...@pekko.apache.org >> >>
