Also https://github.com/apache/incubator-pekko/pull/270 should be added to the list (already reflected in github).
The community has already stated that if Scala 3.3 LTS is ready by the time we wan't to make a RC then Pekko should be released with 3.3 LTS support. Note that this technically doesn't need to be done by the first milestone, we however are not differentiating between milestones, RC's and release in github. On Tue, May 23, 2023 at 2:34 PM Matthew Benedict de Detrich < [email protected]> wrote: > FYI have closed https://github.com/apache/incubator-pekko/issues/23 since > its already been done. > > On Tue, May 23, 2023 at 2:23 PM Claude Warren, Jr > <[email protected]> wrote: > >> > ===== START OF BALLOT === >> > >> > stream: fix regression in JsonFraming >> > <https://github.com/apache/incubator-pekko/pull/44> #44 opened on Nov >> 14, >> > 2022 by jrudolph >> > • Changes requested >> > >> > +1 >> >> >> > Provide an automated migration to migrate from akka to pekko >> > <https://github.com/apache/incubator-pekko/issues/22> nice-to-have >> > (low-prio) >> > #22 opened on Nov 5, 2022 by danischroeter >> > >> >> -1 Nice to have can be added later >> >> >> > Enable github status checks for CI >> > <https://github.com/apache/incubator-pekko/issues/23> >> > #23 opened on Nov 6, 2022 by mdedetrich >> > >> >> -1 As noted in the ticket the system needs to quiesce before we can >> really implement this. It should be placed in the milestone 2 list. >> >> > >> > need to build source distributions >> > <https://github.com/apache/incubator-pekko/issues/78> >> > #78 opened on Dec 23, 2022 by pjfanning >> > >> >> +1 Give it a best shot, ticket does not need to close before milestone1 >> is >> complete. In fact it should probably close when milestone 1 completes. >> >> >> > Automate the release < >> https://github.com/apache/incubator-pekko/issues/85> >> > #85 opened on Jan 5 by pjfanning >> > >> >> -1 This is a nice to have and as I argued on the dev list there is no way >> to automate the release until we know what the release process is. The >> only way to know the release process is to release. So for milestone1 >> this >> is an impossibility. >> >> > >> > >> >> > Remove references to Akka or Lightbend in the doc >> > <https://github.com/apache/incubator-pekko/issues/98> >> > #98 opened on Jan 9 by jchapuis >> > >> >> +1 Give it a best shot, ticket does not need to close before milestone1 >> is >> complete. THis is something that should be identified as needing specific >> review during the RC review process. It should probably close when >> milestone 1 completes. >> >> Create a migration guide to migrate from Akka to Pekko >> > <https://github.com/apache/incubator-pekko/issues/109> >> > #109 opened on Jan 17 by kw217 >> > >> >> -1 Nice to have but not necessary. Can be added later as a site >> documentation update. >> >> >> > Setup the release process >> > <https://github.com/apache/incubator-pekko/issues/130> >> > #130 opened on Jan 26 by jrudolph >> > 9 tasks >> > >> >> +1 Needed to understand what we are releasing and what the process should >> be. This ticket should not close before Milestone1 completes. >> >> Figure out classes that need to be renamed for migration script >> > <https://github.com/apache/incubator-pekko/issues/68> >> > #68 opened on Dec 3, 2022 by mdedetrich >> > >> >> -1 This is a nice to have with respect to RC1. Once we have RC1 writing >> the migration script and releasing it as v1.0.1 might make sense. Release >> early, release often. >> >> >> > Investigate how to scan for problematic licenses >> > <https://github.com/apache/incubator-pekko/issues/151> high >> > priorityrequired for next release >> > #151 opened on Feb 8 by mdedetrich >> > >> >> +0 This issue is open but looks like it could be closed. I do note that >> Justin is correct in that most IPMC members will use RAT to scan for the >> headers, but that can be addressed as part of "Setup the release process" >> >> other source files to add licenses to >> > <https://github.com/apache/incubator-pekko/issues/238> >> > #238 opened on Mar 9 by pjfanning >> > >> >> +1 Try to make sure we have all the licenses in place for the release. >> >> rewrite pekko-platform-guide to use pekko artifacts and to remove Akka >> refs >> > <https://github.com/apache/incubator-pekko/issues/244> good first issue >> > Good for newcomershelp wantedExtra attention is needed >> > #244 opened on Mar 13 by pjfanning >> > >> >> -1 Not needed for RC1. Would be nice to have as part of v1.0.1 or similar >> close follow on. >> >> =act Refactory AsyncDnsResolver to fix the race condition of nextId() >> > <https://github.com/apache/incubator-pekko/pull/288> >> > #288 opened on Apr 14 by He-Pin• Review required >> > >> >> +1 As work is done and just needs review. >> >> >> > Snapshot is missing LICENSE file >> > <https://github.com/apache/incubator-pekko/issues/328> >> > #328 opened 1 minute ago by Claudenw >> > >> >> +1 will fail IPMC review otherwise. >> >> Snapshot missing NOTICE file >> > <https://github.com/apache/incubator-pekko/issues/329> >> > #329 opened 5 minutes ago by Claudenw >> > < >> https://github.com/apache/incubator-pekko/issues?q=is%3Aissue+is%3Aopen+author%3AClaudenw >> > >> > >> >> +1 will fail IPMC review otherwise. >> > > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* [email protected] > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
