cassandra-pr mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mshuler <...@git.apache.org>
Subject [GitHub] cassandra pull request #230: Add developer docs for creating releases
Date Mon, 02 Jul 2018 20:35:00 GMT
Github user mshuler commented on a diff in the pull request:

    https://github.com/apache/cassandra/pull/230#discussion_r199613098
  
    --- Diff: doc/source/development/release_process.rst ---
    @@ -0,0 +1,224 @@
    +.. 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.
    +
    +.. highlight:: none
    +..  release_process:
    +
    +Release Process
    +***************
    +
    +.. contents:: :depth: 3
    +
    +| 
    +|
    +
    +Here Release Managers will find the steps for creating, voting and publishing a release
for Apache Cassandra.
    +A committer can perform the initial steps of creating and calling a vote on a proposed
release, but only a PMC can complete the process of publishing and announcing the release.
    +
    +
    +Prerequisites
    +=============
    +
    +Be familiar with the following
    + * `ASF Release Policy <http://www.apache.org/legal/release-policy.html>`_.
    + * `ASF Release Distribution Policy <http://www.apache.org/dev/release-distribution>`_.
    + * `ASF Release Best Practices <http://www.eu.apache.org/dev/release-publishing.html>`_.
    +
    +
    +A debian based linux OS is required to run the release steps from.
    +
    +
    +Create and publish your GPG key
    +-------------------------------
    +
    +To create a GPG key, follow the `guidelines <http://www.apache.org/dev/openpgp.html>`_.
    +Include your public key in::
    +
    +  https://dist.apache.org/repos/dist/cassandra/KEYS
    +
    +
    +Publish your GPG key in a PGP key server, such as `MIT Keyserver <http://pgp.mit.edu/>`_.
    +
    +
    +Create Release Artifacts
    +========================
    +
    +Any committer can perform the following steps to create and call a vote on a proposed
release.
    +
    +Check that no open jira tickets are urgent and currently being worked on.
    +Also check with a PMC that there's security vulnerabilities currently being worked on
in private.
    +
    +Perform the Release
    +-------------------
    +
    +Run the following commands to generate and upload release artifacts, to a nexus staging
repository and distribution location::
    +
    +    git clone https://github.com/apache/cassandra-builds.git
    +    cd cassandra-build/cassandra-release
    +    # edit the variables at the top of `prepare_release.sh`
    +    ./prepare_release.sh
    --- End diff --
    
    After cloning cassandra-builds repo, the prepare_release.sh is run from the actual cassandra
git checkout, on the branch/commit that we wish to tag for the tentative release along with
version number to tag. For example:
    ```
    cd ~/git/cassandra/
    git checkout cassandra-3.11
    ../cassandra-builds/cassandra-release/prepare_release.sh -v 3.11.3
    ```


---

---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org


Mime
View raw message