Now that we have some infrastructure setup I would like to investigate what it will take to begin publishing snapshot builds. I think it's important to prioritize publishing snapshots so that we can begin soliciting community feedback and update the pekko dependencies of the satellite projects we've brought along (http, connectors, etc.)
Akka projects publish a timestamped snapshot with every merge to master. Snapshots were previously published to a Lightbend bintray repository, but after that was sunset they began publishing to Sonatype's snapshot repository (https://oss.sonatype.org/content/repositories/snapshots). Sonatype admins might clean out snapshots at any time, but in my experience they persist for quite awhile and should satisfy our near-term needs. Please forgive me if some of these things have already been discussed, but I have a few questions. * Have we settled on a common group id for all core and satellite projects? * How will access to publishing to that group id be managed on Sonatype? * Other than the scalafmt PR are there any other housekeeping tasks that need to be completed before we can begin publishing? I've previously setup release-by-tag and snapshot publishing for the alpakka and akka projection projects and I'm eager to volunteer to setup pekko once we have answers to some of these logistical questions. Regards, Sean -- @seg1o <https://twitter.com/seg1o>, seanglover.com
