Pekko Core v1.0.0 Release

Current development is split between trying to get the core Pekko modules ready for a v1.0.0 release and other developers using the Work in Progress of those core modules to make some progress with other Pekko modules (eg Pekko HTTP).

Pekko Core Modules

GitHub project: https://github.com/orgs/apache/projects/220 (only visible to ASF contributors)

GitHub milestones:

• https://github.com/apache/incubator-pekko/milestone/1
• https://github.com/apache/incubator-pekko-sbt-paradox/milestone/1

Pekko Core Release Notes

Headline Work for this release

• Using Pekko module snapshots in other modules to see if they work well
  • We've found some support missing for Scala 2.12 (Akka team were looking to drop this but Pekko is keeping this support)
  • Migrating https://github.com/apache/incubator-pekko-samples
• Getting CI build running
  • https://github.com/apache/incubator-pekko CI builds show some timing issues but things look pretty good
• Migrating docs
  • We're using rsync to put latest docs up on nightles.apache.org every night
    • https://nightlies.apache.org/pekko/docs/
  • Also manually published https://pekko.apache.org/
    • We need to work out if we want to use redirects from this to the nightlies site
    • Or if we want to get INFRA team to support a separate rsync for this site (they may not have the resources for this)
    • Or if we stick with manual publish
  • The core module docs reference docs for some satellite repos and we at least get the 'current' pre-release version of these docs deployed
    • https://github.com/apache/incubator-pekko-http
    • https://github.com/apache/incubator-pekko-grpc
    • https://github.com/apache/incubator-pekko-management
    • https://github.com/apache/incubator-pekko-samples
• Pekko home page (see https://lists.apache.org/thread/n51908lxw2zsj6sz562nfqslfxzxvq2s)
  • A landing page
  • A download page
• Copyrights and Licenses
  • Unable to render Jira issues macro, execution error.
  • Unable to render Jira issues macro, execution error.
• Release Automation
  • We need to document the release process
  • We need to balance the need for some automation while taking account that many of the tasks of the Release Manager are quite manual and having some release automation that has never been used before could be counterproductive. Building the jars and signing them is the easy bit. Going through the ASF procedures and votes is the complicated part.