SDAP Release Management

[lewis john mcgibbney <le...@apache.org>]

Hi dev@,

First and foremost thank you fgreg for stepping into release management
position. This is a real important part of SDAP's incubation and your
leadership is not only important but crucial.
OK so once you've rolled back the existing release candidate e.g. delete
the Github tag's, delete the Docker images, etc. then let's think about how
we can put a release management process together which complies with ASF
release policy [0].

We need to start with understanding the release publishing guidance [1].
Specifically see the sections on the release manager role [2], what
constitutes a valid release and then signing artifacts [4]. Once all of
that has been done and all *source code *artifacts associated with the
release candidate have been signed by the release manager then we move on
to hosting a community VOTE [5].

Subject to a positive binding RESULT, then we progress to release artifact
distribution via www.apache.org [6] and then we move on to publishing the
Docker artifacts under the Apache Dockerhub Org.

All of the above should be documented in a release management guide which
should live on some easily accessible/editable location. In my experience,
*something* always changes during release management process. That's why we
document the process from beginning to end. This takes longer but saves us
time and technical debt in the future.

Please let me know here when you've rolled back the existing RC and are
ready to move on with generating, signing and staging source code release
artifacts.

Thanks fgreg, and again, thanks for stepping up for release manager.

lewismc

[0] https://apache.org/dev/#releases
[1] https://apache.org/dev/release-publishing.html
[2] https://apache.org/dev/release-publishing.html#release_manager
[3] https://apache.org/dev/release-publishing.html#valid
[4] https://apache.org/dev/release-publishing.html#signed
[5] https://apache.org/dev/release-publishing.html#voted
[6] https://apache.org/dev/release-publishing.html#distribution_dist

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: SDAP Release Management

[Joern Kottmann <ko...@gmail.com>]

Hello all,

it would probably be good to look at other Apache projects, and copy
and adapt a release process from them.

For example from OpenNLP:
https://opennlp.apache.org/release.html

Then you can follow the process step by step every time you make a release.

Jörn

On Sat, Feb 2, 2019 at 3:28 AM lewis john mcgibbney <le...@apache.org> wrote:
>
> Hi dev@,
>
> First and foremost thank you fgreg for stepping into release management
> position. This is a real important part of SDAP's incubation and your
> leadership is not only important but crucial.
> OK so once you've rolled back the existing release candidate e.g. delete
> the Github tag's, delete the Docker images, etc. then let's think about how
> we can put a release management process together which complies with ASF
> release policy [0].
>
> We need to start with understanding the release publishing guidance [1].
> Specifically see the sections on the release manager role [2], what
> constitutes a valid release and then signing artifacts [4]. Once all of
> that has been done and all *source code *artifacts associated with the
> release candidate have been signed by the release manager then we move on
> to hosting a community VOTE [5].
>
> Subject to a positive binding RESULT, then we progress to release artifact
> distribution via www.apache.org [6] and then we move on to publishing the
> Docker artifacts under the Apache Dockerhub Org.
>
> All of the above should be documented in a release management guide which
> should live on some easily accessible/editable location. In my experience,
> *something* always changes during release management process. That's why we
> document the process from beginning to end. This takes longer but saves us
> time and technical debt in the future.
>
> Please let me know here when you've rolled back the existing RC and are
> ready to move on with generating, signing and staging source code release
> artifacts.
>
> Thanks fgreg, and again, thanks for stepping up for release manager.
>
> lewismc
>
> [0] https://apache.org/dev/#releases
> [1] https://apache.org/dev/release-publishing.html
> [2] https://apache.org/dev/release-publishing.html#release_manager
> [3] https://apache.org/dev/release-publishing.html#valid
> [4] https://apache.org/dev/release-publishing.html#signed
> [5] https://apache.org/dev/release-publishing.html#voted
> [6] https://apache.org/dev/release-publishing.html#distribution_dist
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc