snapshot releases

[David Morávek <dm...@apache.org>]

Hi,

I've just lost quite some time on the issue related to how we currently
release beam snapshots.

Because we only publish snapshots from the master branch, unreleased
version of beam (2.21.0-SNAPSHOT) was last updated on 9th of April.

eg.
https://repository.apache.org/content/groups/snapshots/org/apache/beam/beam-runners-core-java/2.21.0-SNAPSHOT/

This is may be confusing for the end user and I think we should either:
- Upload snapshots from all release branches.
- Keep only snapshots from current master version (delete all prior
versions) to have user fail fast on CI build.

WDYT?

D.

Re: snapshot releases

[Luke Cwik <lc...@google.com>]

I would suggest keeping only snapshots from the current master version OR
the current master version and any version that is yet to be released
(allowing users to track fixes to a potential release candidate).

We had thought of using the nightly snapshot process to build and generate
our release candidates in the past which would align with the second option.

Since our build process has evolved a lot over the releases and we rarely
patch a release it wouldn't make sense to upload snapshots from all release
branches.

On Wed, May 13, 2020 at 2:57 AM David Morávek <dm...@apache.org> wrote:

> Hi,
>
> I've just lost quite some time on the issue related to how we currently
> release beam snapshots.
>
> Because we only publish snapshots from the master branch, unreleased
> version of beam (2.21.0-SNAPSHOT) was last updated on 9th of April.
>
> eg.
> https://repository.apache.org/content/groups/snapshots/org/apache/beam/beam-runners-core-java/2.21.0-SNAPSHOT/
>
> This is may be confusing for the end user and I think we should either:
> - Upload snapshots from all release branches.
> - Keep only snapshots from current master version (delete all prior
> versions) to have user fail fast on CI build.
>
> WDYT?
>
> D.
>