• don't forget the pekko name in the jars (akka-actor becomes pekko-actor, etc.)
• the guide will go into the docs - there is a placeholder for the migration section in there (or at least once an inflight PR is merged)

Cool, thanks - added that to the description.

Docs location - presumably you're referring to https://github.com/apache/incubator-pekko/blob/main/docs/src/main/paradox/project/migration-guides.md which just got updated? Perfect. Should we just put the migration guide in that doc, rather than a separate doc linked from there?

Example migration (thanks @pjfanning): pjfanning/micrometer-akka#3

Just reviewing the status of this issue, I think that the next steps on this card are to complete the following TODOs:

• Flesh out existing parts of migration guide with more details.
• Address the final three bullets still not covered in issue description.
• Add clear linking from GitHub homepage to migration guide.
• Add clear linking from the project website homepage: The migration guide is on the homepage (index.html) but the link is buried down in the Project Information subheading. Since the large proportion of PEKKO users will initially be migrating from AKKA I think that it is important that we place this in a clearer location e.g. the docs 'Getting Started' Guide.
• Add at link to a clean example migration to this migration guide OR copy snippets of it into the migration guide subsections when we flesh it out.

Following the above, test out the migration guide to identify remaining gaps/issues.

We have a migration guide. It's not perfect but we can adjust it. Please raise PRs if you want to suggest changes - or comment on this issue.

https://pekko.apache.org/docs/pekko/current//project/migration-guides.html

Removing the milestone as I want to not have open issues in it.