> I prefer not to look at Akka repos, including their issues. We should not be looking at the PRs. If we apply a fix to Pekko and it could be construed that the fix is based on an Akka fix, there could be real trouble.
Afaik looking at Akka issues/features is fine but looking at PR's is definitely a no-go legally. > If the person who submitted the PR to Akka can also be persuaded to submit it to Pekko then the whole position is much simpler. Agreed > If there is anything critical to the Pekko 1.0.0 release, it should be logged in Pekko issues tracker. If there is nothing logged there, we will proceed to a 1.0.0 release. Also agreed and as far as I understand there is nothing else that is considered critical which hasn't already been discussed. On Mon, May 22, 2023 at 12:03 PM PJ Fanning <[email protected]> wrote: > I prefer not to look at Akka repos, including their issues. We should > not be looking at the PRs. If we apply a fix to Pekko and it could be > construed that the fix is based on an Akka fix, there could be real > trouble. > > If the person who submitted the PR to Akka can also be persuaded to > submit it to Pekko then the whole position is much simpler. > > If there is anything critical to the Pekko 1.0.0 release, it should be > logged in Pekko issues tracker. If there is nothing logged there, we > will proceed to a 1.0.0 release. > > On Mon, 22 May 2023 at 04:40, kerr <[email protected]> wrote: > > > > Sorry, I mean the first final release of pekko 1.0.0 should include fixes > > for critical issues. > > 何品s > > > > > > kerr <[email protected]> 于2023年5月22日周一 11:37写道： > > > > > I think we should fix some critical issues before the final release of > > > 3.3.0, which was reported to the Akka repo but not pekko. > > > 何品 > > > > > > > > > Justin Mclean <[email protected]> 于2023年5月22日周一 08:57写道： > > > > > >> Hi, > > >> > > >> > If anyone is looking to help push Pekko core libs [1] to a 1.0.0 > > >> release, the most useful thing to do is try out the latest snapshots > [2]. > > >> > > >> That might help from a compatibility point of view, but not from an > ASF > > >> release point of view. An ASF release needs to include certain things > like > > >> a LICENSE and NOTICE file etc. Looking at one of those jars at random > I can > > >> see that the META-INF directory doesn’t include a LICENSE or NOTICE > file. > > >> > > >> Kind Regards, > > >> Justin > > >> --------------------------------------------------------------------- > > >> 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] > > -- 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]
