Johannes Rudolph has sorted out a couple of remaining issues
(including #38). I think that makes it easier to try moving towards
badging an official release for this module.

On Thu, 29 Jun 2023 at 09:13, Matthew Benedict de Detrich
<[email protected]> wrote:
>
> On my side there is one issue I would like to see resolved before we make a
> first release which is
> https://github.com/apache/incubator-pekko-sbt-paradox/issues/38. As you can
> see the issue has been marked as high priority because currently the "copy
> source" button on the docs is completely broken and it does stick out as a
> sore thumb.
>
> On Thu, Jun 29, 2023 at 9:02 AM Nicolas Vollmar <[email protected]> wrote:
>
> > Makes sense, +1
> >
> > On Wed, 28 Jun 2023 at 20:52, PJ Fanning <[email protected]> wrote:
> >
> > > Hi everyone,
> > >
> > > sbt-paradox-pekko [1] is fairly stable. It would be nice to have an
> > > official 1.0.0 release instead of relying on snapshots.
> > >
> > > I have a thread on the Incubator general list [2] asking if we need to
> > > go though the full voting cycle for this. sbt-paradox-pekko is just an
> > > internal Pekko build tool and may not need the full process that is
> > > needed to release the public facing repos like the Pekko core repo.
> > >
> > > Any objections to proceeding to an sbt-paradox-pekko release?
> > >
> > >
> > > [1] https://github.com/apache/incubator-pekko-sbt-paradox
> > > [2] https://lists.apache.org/thread/b172od7g664zwbl14242r4vtmzghdtn9
> > >
> > > ---------------------------------------------------------------------
> > > 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]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to