The license header task is one of the ones that is in progress already
- see https://github.com/apache/incubator-pekko/pull/50

On Fri, 6 Jan 2023 at 11:16, Mehmet Salgar <[email protected]> wrote:
>
>
>
> Hi,
>
> I like to start with
>
> >* getting the Apache license headers into the source files
>
> https://github.com/apache/incubator-pekko/issues/38#issuecomment-1319945818
>
> Is that the text we have to use now?
>
> Regards
>
>
> Gesendet: Donnerstag, 05. Januar 2023 um 16:16 Uhr
> Von: "PJ Fanning" <[email protected]>
> An: [email protected]
> Betreff: M0 release for incubator-pekko repo
> Hi everyone,
>
> I'm going to ignore that there are other pekko git repos. A lot of the
> same work needs to be done for those repos but it simplifies the
> conversation to ignore them in this thread. We can come back to them
> later.
>
> There has been good progress but there is a lot still to do. Some of
> the key issues remaining include.
> * getting the Apache license headers into the source files
> * getting the nightlies published
> * getting the doc site up
> * careful review of the docs to remove any remaining references to
> Lightbend or Akka (including logos)
> * new look and feel for the docs (just so they don't look exactly like
> the Akka ones)
> * review the automated test failures
> * source and binary distributions
> (https://github.com/apache/incubator-pekko/issues/78)
> * upgrade dependency jars if they have CVEs (unless we need to make
> major changes to facilitate the upgrade)
>
> Some of these tasks are in progress but most of the tasks could be
> taken on by willing volunteers.
>
> There may be an argument that we could try an early M0 or M1 release
> to allow outside lib maintainers and other interested parties to try
> out the new libs. There are probably not many of the items above that
> could be delayed to a later milstone though - possibly some of the doc
> and test tasks.
>
> ---------------------------------------------------------------------
> 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]

Reply via email to