henrikingo commented on code in PR #114: URL: https://github.com/apache/otava/pull/114#discussion_r2637791852
########## docs/RELEASE.md: ########## @@ -0,0 +1,490 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + --> + +# Creating Apache Otava Release + +> [!TIP] +> This document is based on the release guide of [Apache Flink project](https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release). + +## Introduction + +The Otava community treats releases with great importance. They are a public face of the project and most users interact with the project only through the releases. Releases are signed off by the entire Otava community in a public vote. +Each release is executed by a Release Manager, who is selected/proposed by the Otava PMC members. This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the [[email protected]](mailto:[email protected]) mailing list. + +Please remember that publishing software has legal consequences. This guide complements the foundation-wide [Product Release Policy](https://www.apache.org/dev/release.html) and [Release Distribution Policy](https://www.apache.org/dev/release-distribution). Review Comment: I would maybe soften but also broaden the first sentence. (But maybe as you now live in an English speaking country, I'll leave final judgement to you): Please remember, that the act of publishing software has both legal and policy significance. ########## docs/RELEASE.md: ########## @@ -0,0 +1,490 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + --> + +# Creating Apache Otava Release + +> [!TIP] +> This document is based on the release guide of [Apache Flink project](https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release). + +## Introduction + +The Otava community treats releases with great importance. They are a public face of the project and most users interact with the project only through the releases. Releases are signed off by the entire Otava community in a public vote. +Each release is executed by a Release Manager, who is selected/proposed by the Otava PMC members. This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the [[email protected]](mailto:[email protected]) mailing list. + +Please remember that publishing software has legal consequences. This guide complements the foundation-wide [Product Release Policy](https://www.apache.org/dev/release.html) and [Release Distribution Policy](https://www.apache.org/dev/release-distribution). + +## Overview + +### What is in Apache Otava Release + +Apache Otava release consists of: +* ASF source zips archived on [dist.apache.org](dist.apache.org). +* PyPI wheels published to [pypi.org](https://pypi.org/project/apache-otava/). +* Docker images published to [Dockerhub](https://hub.docker.com/r/apache/otava). +* Release tag on [GitHub](https://github.com/apache/otava/releases). + +### Phases of the release + +The release process consists of several steps: +1. Decide to release +2. Prepare for the release +3. Build a release candidate +4. Vote on the release candidate Review Comment: 4b) While we are in the ASF incubator program, voting has 2 phases: On the Otava project mailing list, then formally on the Incubator project list. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
