There has been lots of discussion about what goes into the milestone but I am ok with cancelling this to open a discussion about each item if that is what you want to do. How do you propose we discuss each item?
On Fri, May 26, 2023 at 12:14 PM PJ Fanning <[email protected]> wrote: > There was no discuss thread before this vote - I don't think this is > following procedure. > > On Fri, 26 May 2023 at 11:54, Claude Warren, Jr > <[email protected]> wrote: > > > > This vote will close at 00:00 GMT June 1 > > > > On Wed, May 24, 2023 at 4:05 PM Claude Warren, Jr < > [email protected]> > > wrote: > > > > > Please take none vote statements to a new email topic. > > > > > > On Wed, May 24, 2023 at 3:53 PM PJ Fanning <[email protected]> > wrote: > > > > > >> Just a note but the issues in the 1.0.0 milestone are not the be all > > >> and end all. We're still discovering new items that we need for a > > >> 1.0.0 release. Have a look at the milestone [1] for the latest issues. > > >> > > >> I would really prefer if the relative merits of whether these are > > >> blockers for 1.0.0 release are discussed on the individual issues in > > >> GitHub instead of having one email thread that has many different > > >> topics in it. > > >> > > >> [1] > > >> > https://github.com/apache/incubator-pekko/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0 > > >> > > >> > > >> > > >> On Wed, 24 May 2023 at 15:47, Sean Glover <[email protected]> > wrote: > > >> > > > >> > I agree it shouldn't hold up a release, but I wanted to identify it > as a > > >> > common migration concern. My work codebase contains > akka-typed-actor, > > >> > akka-streams, akka-http, Kamon, tapir, various alpakka connectors > and > > >> other > > >> > 3rd party libs that depend on akka. I'll set aside some time to try > and > > >> > concurrently run some of our core akka things soon. > > >> > > > >> > On Wed, May 24, 2023 at 9:33 AM PJ Fanning <[email protected]> > wrote: > > >> > > > >> > > > A big item I > > >> > > > haven't seen discussed yet is what are the caveats of running > akka > > >> and > > >> > > > pekko on the same classpath? > > >> > > > > >> > > We've switched all the code to use org.apache.pekko packages. > We've > > >> > > changed the config names to use 'pekko' prefix. We've changed the > > >> > > default ports. > > >> > > > > >> > > There is one thread about the compatibility of akka and pekko > > >> persistence > > >> > > [1]. > > >> > > > > >> > > Something might be missed. > > >> > > > > >> > > In the end of the day, it's hard to envision what someone who uses > > >> > > wants to use Akka and Pekko in the same JVM will run up against. > If > > >> > > someone hits an issue, report it and we'll look at it. > > >> > > > > >> > > If someone wants to spend time trying out some scenarios that > might > > >> > > affect them - that would be really appreciated by the community, > > >> > > especially if they report back on what they've tried and how they > got > > >> > > on. > > >> > > > > >> > > Someone who wants to use Akka stream connectors with Pekko stream > > >> > > connectors would probably need to do so at the reactivestreams API > > >> > > level. > > >> > > > > >> > > Ultimately, there is so much that we could worry about but we > really > > >> > > do need to make a release. The longer we delay a release, the > greater > > >> > > the likelihood that users will abandon Akka and Pekko altogether. > > >> > > > > >> > > [1] > https://lists.apache.org/thread/v7c08l4bn66o4o2go0h7xzzl8pz0tr6p > > >> > > > > >> > > > > >> > > > > >> > > On Wed, 24 May 2023 at 13:32, Sean Glover <[email protected]> > > >> wrote: > > >> > > > > > >> > > > On Tue, May 23, 2023 at 6:58 AM Claude Warren, Jr > > >> > > > <[email protected]> wrote: > > >> > > > > > >> > > > > The following tickets are currently included in milestone 1. > > >> Please > > >> > > vote > > >> > > > > to retain (+1) or remove (-1) for items that you feel strongly > > >> about. > > >> > > This > > >> > > > > is a simple vote more +1 than -1 indicates that the item will > be > > >> > > retained > > >> > > > > in the milestone. If you want to add more items to the > milestone > > >> then > > >> > > > > please open a vote discussion for them separately before > adding > > >> them. > > >> > > > > > > >> > > > > A removal from the milestone does not remove the ticket from > later > > >> > > > > consideration. The final list should be item that are > necessary > > >> for > > >> > > the > > >> > > > > RC1 to be built > > >> > > > > > > >> > > > > Thanks, > > >> > > > > Claude > > >> > > > > > > >> > > > > ===== 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 > > >> > > > > > > >> > > > > 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 > > >> > > > > > >> > > > > > >> > > > > Enable github status checks for CI > > >> > > > > <https://github.com/apache/incubator-pekko/issues/23> > > >> > > > > #23 opened on Nov 6, 2022 by mdedetrich > > >> > > > > > > >> > > > > need to build source distributions > > >> > > > > <https://github.com/apache/incubator-pekko/issues/78> > > >> > > > > #78 opened on Dec 23, 2022 by pjfanning > > >> > > > > > > >> > > > > > > >> > > > -1 The path forward doesn't look trivial so I think deferring > this > > >> makes > > >> > > > sense. > > >> > > > > > >> > > > > > >> > > > > Automate the release < > > >> > > https://github.com/apache/incubator-pekko/issues/85> > > >> > > > > #85 opened on Jan 5 by pjfanning > > >> > > > > > > >> > > > > > > >> > > > 0 I think this needs to be a fast follow, but not necessary for > this > > >> > > > release. Aside from being error prone, a manual release process > > >> will silo > > >> > > > release knowledge in only a few minds and could hinder prompt > and > > >> regular > > >> > > > releases. > > >> > > > > > >> > > > > > >> > > > > 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 This seems prudent. Is there any roadblock here? > > >> > > > > > >> > > > > > >> > > > > > > >> > > > > 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 > > >> > > > > > > >> > > > > > >> > > > 0 I don't think a full fledged migration guide is needed right > now, > > >> but > > >> > > > some guidance for existing akka users would be useful. Maybe > this > > >> could > > >> > > be > > >> > > > represented along with a release announcement or blog post. A > big > > >> item I > > >> > > > haven't seen discussed yet is what are the caveats of running > akka > > >> and > > >> > > > pekko on the same classpath? For legacy akka integrations this > will > > >> > > likely > > >> > > > be the scenario for some time as we incrementally release akka > > >> satellite > > >> > > > projects and as 3rd party libraries update (if they update at > all). > > >> > > > > > >> > > > > > >> > > > > > > >> > > > > Setup the release process > > >> > > > > <https://github.com/apache/incubator-pekko/issues/130> > > >> > > > > #130 opened on Jan 26 by jrudolph > > >> > > > > 9 tasks > > >> > > > > > > >> > > > > 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 > > >> > > > > > > >> > > > > 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 > > >> > > > > > > >> > > > > other source files to add licenses to > > >> > > > > <https://github.com/apache/incubator-pekko/issues/238> > > >> > > > > #238 opened on Mar 9 by pjfanning > > >> > > > > > > >> > > > > 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 > > >> > > > > > > >> > > > > =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 > > >> > > > > > > >> > > > > Snapshot is missing LICENSE file > > >> > > > > <https://github.com/apache/incubator-pekko/issues/328> > > >> > > > > #328 opened 1 minute ago by Claudenw > > >> > > > > > > >> > > > > > >> > > > +1 > > >> > > > > > >> > > > > > > >> > > > > 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 > > >> > > > > >> > > > --------------------------------------------------------------------- > > >> > > To unsubscribe, e-mail: [email protected] > > >> > > For additional commands, e-mail: [email protected] > > >> > > > > >> > > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
