[jira] [Commented] (MESOS-756) Improve release tooling.

["Vinod Kone (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857140#comment-13857140 ] 

Vinod Kone commented on MESOS-756:
----------------------------------

I propose we do this is as follows:

1) A script for tagging rc (support/tag.sh)
 --> Edit configure.ac to include release candidate version (e.g., 0.15.0-rc4)
 --> make distcheck
 --> git push tag
 --> build & deploy the jar to maven staging repo and *release* it.

2) A script for voting rc (support/vote.sh)
 --> git checkout release version tag
 --> Check configure.ac has the correct version (shouldn't include the release candidate version e.g., 0.15.0)
 --> make distcheck
 --> build & deploy the jar to mave staging repo and *close* (but not release) it
 --> svn commit the tarball and sigs to *dev* repo
 --> Generate email template to be sent to dev@mesos.a.o

3) A script to release rc after the vote passes (support/release.sh)
 --> svn co dev repo
 --> mv dev to release
 --> svn ci release repo
 --> Release the maven staging repo
 --> Generate email template to be sent to dev@meso.a.o

Thoughts?


> Improve release tooling.
> ------------------------
>
>                 Key: MESOS-756
>                 URL: https://issues.apache.org/jira/browse/MESOS-756
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benjamin Mahler
>            Assignee: Vinod Kone
>             Fix For: 0.16.0
>
>
> We currently have support/release.sh which is actually for building a release candidate and calling a vote. We should improve this script to add some of the missing steps:
> Before starting:
> 1. Include a prompt for having your gpg key inside dist/release/mesos/KEYS
> 2. Validate that configure.ac contains the intended version.
> After building the release candidate:
> 2. make maven-install
> 3. mvn deploy -f src/java/mesos.pom
> 4. Prompt to close the staging maven repository and request the user to provide the link (for generating a sample [VOTE] email body).
> 5. svn commit the release to dist/dev/mesos instead of scp'ing it into people.apache.org.
> 5. Provide a sample [VOTE] email.
> It would be nice to also have tooling for the post-vote process:
> 1. svn mv the candidate from dist/dev/mesos/ to dist/release/mesos
> 2. Prompt to release the closed staging repository on maven.
> 3. Prompt to close the JIRA for the release.
> 4. Prompt to update the website for the release.
> 5. Provide a sample [VOTE][RESULT] email body.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)