Publishing snapshots

[Sean Glover <se...@seanglover.com>]

Now that we have some infrastructure setup I would like to investigate what
it will take to begin publishing snapshot builds. I think it's important to
prioritize publishing snapshots so that we can begin soliciting community
feedback and update the pekko dependencies of the satellite projects we've
brought along (http, connectors, etc.)

Akka projects publish a timestamped snapshot with every merge to master.
Snapshots were previously published to a Lightbend bintray repository, but
after that was sunset they began publishing to Sonatype's snapshot
repository (https://oss.sonatype.org/content/repositories/snapshots).
Sonatype admins might clean out snapshots at any time, but in my experience
they persist for quite awhile and should satisfy our near-term needs.

Please forgive me if some of these things have already been discussed, but
I have a few questions.

* Have we settled on a common group id for all core and satellite projects?
* How will access to publishing to that group id be managed on Sonatype?
* Other than the scalafmt PR are there any other housekeeping tasks that
need to be completed before we can begin publishing?

I've previously setup release-by-tag and snapshot publishing for the
alpakka and akka projection projects and I'm eager to volunteer to setup
pekko once we have answers to some of these logistical questions.

Regards,
Sean

-- 
@seg1o <https://twitter.com/seg1o>, seanglover.com

Re: Publishing snapshots

[Sean Glover <se...@seanglover.com>]

Snapshots are now being published to a maven repository on the Apache
Nightlies webserver, https://nightlies.apache.org/pekko/snapshots/

A cron GitHub Action will publish a snapshot each day and enforce that only
the last 30 versions are managed.

On Fri, Nov 11, 2022 at 11:05 AM Sean Glover <se...@seanglover.com> wrote:

> An update, I was asked to create an infra Jira to setup access. I'm not
> sure what kind of turnaround time to expect, but I'll begin working on the
> nightly publish GH action when it's complete.
>
> https://issues.apache.org/jira/browse/INFRA-23895
>
> On Sat, Nov 5, 2022 at 7:48 PM Sean Glover <se...@seanglover.com> wrote:
>
>> Justin, to get more information about the nightlies server, the initial
>> setup of pekko, and configuring the rsync credentials in the pekko
>> repositories, do I just message the users@infra list?
>>
>> On Thu, Nov 3, 2022 at 10:11 AM Sean Glover <se...@seanglover.com> wrote:
>>
>>> Thanks. Apache's nightlies repo looks like the perfect fit. We'll have
>>> to use different means to publish snapshots from (pre-)releases, but given
>>> that akka's already setup to publish to sonatype and the Apache infra team
>>> will help us publish to nightlies there shouldn't be a lot of work to do on
>>> our side.
>>>
>>> On Thu, Nov 3, 2022 at 4:46 AM Johannes Rudolph <
>>> johannes.rudolph@gmail.com> wrote:
>>>
>>>> Seems like https://nightlies.apache.org/ might be the right place to
>>>> put nightlies / snapshots into. There is
>>>> https://nightlies.apache.org/ghactions-publish-rsync.html which
>>>> explains how to use it from ghactions.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>>>> For additional commands, e-mail: dev-help@pekko.apache.org
>>>>
>>>>
>>>
>>> --
>>> @seg1o <https://twitter.com/seg1o>, seanglover.com
>>>
>>

Re: Publishing snapshots

[Sean Glover <se...@seanglover.com>]

An update, I was asked to create an infra Jira to setup access. I'm not
sure what kind of turnaround time to expect, but I'll begin working on the
nightly publish GH action when it's complete.

https://issues.apache.org/jira/browse/INFRA-23895

On Sat, Nov 5, 2022 at 7:48 PM Sean Glover <se...@seanglover.com> wrote:

> Justin, to get more information about the nightlies server, the initial
> setup of pekko, and configuring the rsync credentials in the pekko
> repositories, do I just message the users@infra list?
>
> On Thu, Nov 3, 2022 at 10:11 AM Sean Glover <se...@seanglover.com> wrote:
>
>> Thanks. Apache's nightlies repo looks like the perfect fit. We'll have to
>> use different means to publish snapshots from (pre-)releases, but given
>> that akka's already setup to publish to sonatype and the Apache infra team
>> will help us publish to nightlies there shouldn't be a lot of work to do on
>> our side.
>>
>> On Thu, Nov 3, 2022 at 4:46 AM Johannes Rudolph <
>> johannes.rudolph@gmail.com> wrote:
>>
>>> Seems like https://nightlies.apache.org/ might be the right place to
>>> put nightlies / snapshots into. There is
>>> https://nightlies.apache.org/ghactions-publish-rsync.html which
>>> explains how to use it from ghactions.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>>> For additional commands, e-mail: dev-help@pekko.apache.org
>>>
>>>
>>
>> --
>> @seg1o <https://twitter.com/seg1o>, seanglover.com
>>
>

Re: Publishing snapshots

[Sean Glover <se...@seanglover.com>]

Justin, to get more information about the nightlies server, the initial
setup of pekko, and configuring the rsync credentials in the pekko
repositories, do I just message the users@infra list?

On Thu, Nov 3, 2022 at 10:11 AM Sean Glover <se...@seanglover.com> wrote:

> Thanks. Apache's nightlies repo looks like the perfect fit. We'll have to
> use different means to publish snapshots from (pre-)releases, but given
> that akka's already setup to publish to sonatype and the Apache infra team
> will help us publish to nightlies there shouldn't be a lot of work to do on
> our side.
>
> On Thu, Nov 3, 2022 at 4:46 AM Johannes Rudolph <
> johannes.rudolph@gmail.com> wrote:
>
>> Seems like https://nightlies.apache.org/ might be the right place to
>> put nightlies / snapshots into. There is
>> https://nightlies.apache.org/ghactions-publish-rsync.html which
>> explains how to use it from ghactions.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>> For additional commands, e-mail: dev-help@pekko.apache.org
>>
>>
>
> --
> @seg1o <https://twitter.com/seg1o>, seanglover.com
>

Re: Publishing snapshots

[Sean Glover <se...@seanglover.com>]

Thanks. Apache's nightlies repo looks like the perfect fit. We'll have to
use different means to publish snapshots from (pre-)releases, but given
that akka's already setup to publish to sonatype and the Apache infra team
will help us publish to nightlies there shouldn't be a lot of work to do on
our side.

On Thu, Nov 3, 2022 at 4:46 AM Johannes Rudolph <jo...@gmail.com>
wrote:

> Seems like https://nightlies.apache.org/ might be the right place to
> put nightlies / snapshots into. There is
> https://nightlies.apache.org/ghactions-publish-rsync.html which
> explains how to use it from ghactions.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>

-- 
@seg1o <https://twitter.com/seg1o>, seanglover.com

Re: Publishing snapshots

[Johannes Rudolph <jo...@gmail.com>]

Seems like https://nightlies.apache.org/ might be the right place to
put nightlies / snapshots into. There is
https://nightlies.apache.org/ghactions-publish-rsync.html which
explains how to use it from ghactions.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org

Re: Publishing snapshots

[Johannes Rudolph <jo...@gmail.com>]

Hi,

the existing infrastructure already uses sbt-dynver, so in general
publishing snapshots with sensible IDs is already set up.

I do not think we should publish snaphots to public maven central. It
clutters the public repo and it also seems to be discouraged according
to the apache release-policy that Justin linked above ("they should
not be hosted or linked on pages intended for end users"). Even
assuming Maven Central has unlimited space, it might still have
consequences in terms of how build tools interact with listings of
versions, size of the full catalog etc. So, let's not stress public
infrastructure just like that.

The only reason wanting to put them there is to make it easier for
downstream consumers to test these snapshots out earlier (without
having to add extra repositories to the build). However, this is
exactly the kind of hurdle we want to distinguish snapshots from
(pre-)releases. If we reach the point where we think there's value in
a wider community trying out early versions we can and should release
a beta or RC version. Everyone else can try out snapshots before with
a little bit of extra effort involved.

Johannes

On Thu, Nov 3, 2022 at 7:12 AM Alexandru Nedelcu <al...@apache.org> wrote:
>
> We could also publish builds with a commit-sha version, via something like sbt-dynver [0]. It has the downside that it pollutes Maven Central, but the published artifacts are reliable.
>
> [0]: https://github.com/sbt/sbt-dynver
>
> On Thu, Nov 3, 2022, at 05:27, Sean Glover wrote:
> > Now that we have some infrastructure setup I would like to investigate what
> > it will take to begin publishing snapshot builds. I think it's important to
> > prioritize publishing snapshots so that we can begin soliciting community
> > feedback and update the pekko dependencies of the satellite projects we've
> > brought along (http, connectors, etc.)
> >
> > Akka projects publish a timestamped snapshot with every merge to master.
> > Snapshots were previously published to a Lightbend bintray repository, but
> > after that was sunset they began publishing to Sonatype's snapshot
> > repository (https://oss.sonatype.org/content/repositories/snapshots).
> > Sonatype admins might clean out snapshots at any time, but in my experience
> > they persist for quite awhile and should satisfy our near-term needs.
> >
> > Please forgive me if some of these things have already been discussed, but
> > I have a few questions.
> >
> > * Have we settled on a common group id for all core and satellite projects?
> > * How will access to publishing to that group id be managed on Sonatype?
> > * Other than the scalafmt PR are there any other housekeeping tasks that
> > need to be completed before we can begin publishing?
> >
> > I've previously setup release-by-tag and snapshot publishing for the
> > alpakka and akka projection projects and I'm eager to volunteer to setup
> > pekko once we have answers to some of these logistical questions.
> >
> > Regards,
> > Sean
> >
> > --
> > @seg1o <https://twitter.com/seg1o>, seanglover.com
>
> --
> Alexandru Nedelcu
> alexn.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org

Re: Publishing snapshots

[Justin Mclean <ju...@classsoftware.com>]

Hi,

You do need to take a little care in publishing snapshots or other unreleased code. [1] There is also this [2].

Kind Regards,
Justin

1. https://www.apache.org/legal/release-policy.html#publication <https://www.apache.org/legal/release-policy.html#publication>
2. https://nightlies.apache.org <https://nightlies.apache.org/>

Re: Publishing snapshots

[Alexandru Nedelcu <al...@apache.org>]

We could also publish builds with a commit-sha version, via something like sbt-dynver [0]. It has the downside that it pollutes Maven Central, but the published artifacts are reliable.

[0]: https://github.com/sbt/sbt-dynver

On Thu, Nov 3, 2022, at 05:27, Sean Glover wrote:
> Now that we have some infrastructure setup I would like to investigate what
> it will take to begin publishing snapshot builds. I think it's important to
> prioritize publishing snapshots so that we can begin soliciting community
> feedback and update the pekko dependencies of the satellite projects we've
> brought along (http, connectors, etc.)
>
> Akka projects publish a timestamped snapshot with every merge to master.
> Snapshots were previously published to a Lightbend bintray repository, but
> after that was sunset they began publishing to Sonatype's snapshot
> repository (https://oss.sonatype.org/content/repositories/snapshots).
> Sonatype admins might clean out snapshots at any time, but in my experience
> they persist for quite awhile and should satisfy our near-term needs.
>
> Please forgive me if some of these things have already been discussed, but
> I have a few questions.
>
> * Have we settled on a common group id for all core and satellite projects?
> * How will access to publishing to that group id be managed on Sonatype?
> * Other than the scalafmt PR are there any other housekeeping tasks that
> need to be completed before we can begin publishing?
>
> I've previously setup release-by-tag and snapshot publishing for the
> alpakka and akka projection projects and I'm eager to volunteer to setup
> pekko once we have answers to some of these logistical questions.
>
> Regards,
> Sean
>
> -- 
> @seg1o <https://twitter.com/seg1o>, seanglover.com

-- 
Alexandru Nedelcu
alexn.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org