Return-Path: 
 <mesos-dev-return-9398-apmail-incubator-mesos-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7EA3710277
	for <apmail-incubator-mesos-dev-archive@minotaur.apache.org>;
 Wed,  5 Jun 2013 20:37:26 +0000 (UTC)
Received: (qmail 9131 invoked by uid 500); 5 Jun 2013 20:37:26 -0000
Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org
Received: (qmail 9092 invoked by uid 500); 5 Jun 2013 20:37:26 -0000
Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mesos-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:mesos-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:mesos-dev@incubator.apache.org>
List-Id: <mesos-dev.incubator.apache.org>
Reply-To: mesos-dev@incubator.apache.org
Delivered-To: mailing list mesos-dev@incubator.apache.org
Received: (qmail 9084 invoked by uid 99); 5 Jun 2013 20:37:26 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2013 20:37:26 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 bernardo.gomezpalacio@gmail.com designates 209.85.160.47 as permitted sender)
Received: from [209.85.160.47] (HELO mail-pb0-f47.google.com) (209.85.160.47)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2013 20:37:22 +0000
Received: by mail-pb0-f47.google.com with SMTP id rr4so2293111pbb.20
        for <mesos-dev@incubator.apache.org>;
 Wed, 05 Jun 2013 13:37:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :message-id:references:to:x-mailer;
        bh=p0MhC8POpgxcpX3DnFlMNj0keAh22c8JAbuI2Dv9mJM=;
        b=mSkPk4gr9UFUyDzJo30eg18dCHnK8PFitzsgSxy4sU8M8NZsXq7jOJXZK93ERgXc38
         UBWk5pLu/OzQSpq2rkU6YOHl/S0MnbRDxWJdbswVEDB577RfbzkYhfoGbV0XCcHkEUi+
         Rd5IPHL16Gfku8FC97X1woLcjxadBfTw2VIuutUjf5lkvmrBQ235l0D3UpPz7ZO6bZrS
         2PMMi4PHYe+tnNQ2hbEVWlvtVSZ2pl70dk2HXrRGLG+4Y10UaR0B1Vg9rCp2nwxkT8sc
         +Y/Q4WpkeWw7NH14N5gEReP30jl3fX1BZL0YUuM1ZXuZkfmozvBOjtMU4Vng2KuON70J
         N8sA==
X-Received: by 10.66.162.67 with SMTP id xy3mr35329855pab.94.1370464622225;
        Wed, 05 Jun 2013 13:37:02 -0700 (PDT)
Received: from [172.20.21.160] (50-193-59-202-static.hfc.comcastbusiness.net.
 [50.193.59.202])
        by mx.google.com with ESMTPSA id p2sm5553585pag.22.2013.06.05.13.37.01
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 05 Jun 2013 13:37:01 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_A902249F-78F3-4A82-B370-BF9368D7A460"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [DISCUSS] Release process
From: Bernardo Gomez Palacio <bernardo.gomezpalacio@gmail.com>
In-Reply-To: 
 <CAAkWvAxgc4yzMD3TVgRediqb7brhcWBA856F4pMMA4ciWz63Lw@mail.gmail.com>
Date: Wed, 5 Jun 2013 13:36:59 -0700
Cc: Benjamin Hindman <benh@berkeley.edu>,
 Benjamin Mahler <benjamin.mahler@gmail.com>
Message-Id: <E520F262-9676-456F-815C-0530A65FCA3B@gmail.com>
References: 
 <CA+8RcoRjw3Om=Zg0rROMp7aDawsdXExAVaJwtki5PC4-t=bd=w@mail.gmail.com>
 <CDD3F482.D4D1F%chris.a.mattmann@jpl.nasa.gov>
 <CA+8RcoRdPAVY+=NhXtYmCq+qmo3OKTooXuX9xUURVx-RCxYLcg@mail.gmail.com>
 <CAFeOQnUtJwR=G2YPeFgStRNn8JD_B0kqg3K6O0i2bOvbhNud+g@mail.gmail.com>
 <CAAkWvAxgc4yzMD3TVgRediqb7brhcWBA856F4pMMA4ciWz63Lw@mail.gmail.com>
To: mesos-dev@incubator.apache.org
X-Mailer: Apple Mail (2.1503)
X-Virus-Checked: Checked by ClamAV on apache.org

--Apple-Mail=_A902249F-78F3-4A82-B370-BF9368D7A460
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

No attempt to add fuss but have you reviewed `git flow`?
https://github.com/nvie/gitflow
http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/

Best
Bernardo.
=3D=3D=3D=3D=3D=3D=3D=3D
Sr. Software Eng. @ Guavus Inc.
@berngp

On Jun 5, 2013, at 1:34 PM, Vinod Kone <vinodkone@gmail.com> wrote:

> SGTM. Though, I have one question?
>=20
> What if there is a bad commit message in 0.12.(z-1)-rcN that you want =
to
> amend in 0.12.z-rc1 ? Would we not allow this? Is the requirement =
going to
> be that a non-fast-forward 0.12.(z-1)-rc(N+1) be released first and =
then
> base 0.12.z-rc1 be based off that?
>=20
>=20
> On Wed, Jun 5, 2013 at 1:22 PM, Benjamin Hindman <benh@berkeley.edu> =
wrote:
>=20
>> Thanks for capturing the discussion Ben. A few thoughts inline.
>>=20
>> The process would be as follows:
>>>=20
>>> 1. Tag a candidate: 0.12.0-rc1.
>>> 2. Call a VOTE to release RC1.
>>> 3. If successful, release and tag 0.12.0 from 0.12.0-rc1.
>>> 4. Otherwise, progress with 0.12.0-rc2 by creating a local branch =
off of
>>> 0.12.0-rc1 and applying the necessary commits.
>>>=20
>>=20
>> I don't think that 0.12.0-rc2 needs to be branched off of 0.12.0-rc1. =
For
>> example, we might want to fix a commit message from 0.12.0-rc1 for
>> 0.12.0-rc2 which means that 0.12.0-rc2 will be divergent from =
0.12.0-rc1.
>> We should always make 0.12.z-rcN be branched off of 0.12.(z-1), but =
not
>> have that requirement for candidates (they are just a "candidate" =
after
>> all).
>>=20
>> Other than that, this all SGTM!
>>=20
>>=20
>>=20
>>=20
>>>=20
>>> History can be seen using 'git log 0.12.0-rc1..0.12.0-rc2'.
>>>=20
>>> This means tags are immutable, and a source of truth for the RCs and
>>> releases.
>>>=20
>>> For now, I will be punting on removing the 0.12.x branch, and will =
simply
>>> create a 0.12.0-rc1 tag to call a VOTE with. But I'd like to gather
>>> thoughts, +1's or -1's.
>>>=20
>>> There's no documentation that I know of. So, yes documenting the
>>>> checklist is a great idea.
>>>> Also note, that we create branches of the form "0.12.x" instead of
>>>> "0.12.0". This makes it easy to cherry pick commits for future bug =
fix
>>>> releases and release candidates.
>>>> Also, you might want to checkout the release.sh script (if there =
are
>>>> some updates to it) from the master branch into 0.12.x.
>>>=20
>>>=20
>>>=20
>>> On Tue, Jun 4, 2013 at 7:50 PM, Mattmann, Chris A (398J) <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>=20
>>>> Looking good, Ben M!
>>>>=20
>>>> Thanks for throwing this up! I've prefixed the subject line
>>>> with a [DISCUSS] thread. Not a requirement by any means but
>>>> makes it nice when looking in mail-archives.apache.org and
>>>> other threaded browsers to see like minded discussion threads :)
>>>>=20
>>>> So, putting this up on a wiki would be great.
>>>> Looking at:
>>>>=20
>>>> http://incubator.apache.org/projects/mesos.html
>>>>=20
>>>>=20
>>>> We have a confluence wiki here:
>>>>=20
>>>> https://cwiki.apache.org/confluence/display/MESOS/Index
>>>>=20
>>>>=20
>>>> I don't have karma to edit it (need to remove the docs exist
>>>> at Github part). I'm working with infra to get karma. Once I
>>>> get it we should add a release process page there that simply
>>>> copies the below :)
>>>>=20
>>>> Either way +1 to proceed with step #1.
>>>>=20
>>>> Cheers,
>>>> Chris
>>>>=20
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW:  http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> -----Original Message-----
>>>> From: Benjamin Mahler <benjamin.mahler@gmail.com>
>>>> Reply-To: "mesos-dev@incubator.apache.org" <
>>>> mesos-dev@incubator.apache.org>
>>>> Date: Tuesday, June 4, 2013 7:23 PM
>>>> To: Benjamin Hindman <benh@berkeley.edu>, Vinod Kone <
>>>> vinodkone@gmail.com>
>>>> Cc: "mesos-dev@incubator.apache.org" =
<mesos-dev@incubator.apache.org>
>>>> Subject: Release process.
>>>>=20
>>>>> Now that 0.11.0 is out, we should continue freeing up the backlog =
and
>>>>> proceed with 0.12.0. I'll be taking care of this release and I'd =
like to
>>>>> document the release process to make it easier for others to help =
out
>>>> with
>>>>> releases in the future. Is there already documentation somewhere? =
Here's
>>>>> what I've inferred:
>>>>>=20
>>>>> 1. First I'll gather the JIRA tickets for the CHANGELOG.
>>>>>=20
>>>>> 2. Send out a review / commit the CHANGELOG updates.
>>>>>=20
>>>>> 3. Cherry pick the CHANGELOG onto 0.12.0.
>>>>>=20
>>>>> 4. Run 'git checkout 0.12.0 && ./support/release.sh 0.12.0 1'.
>>>>>=20
>>>>> 5. Mail general@incubator.apache.org and
>>>>> mesos-dev@incubator.apache.orgcalling a VOTE.
>>>>>=20
>>>>> 6. After a successful VOTE, add it to the website(s)?
>>>>>=20
>>>>> 7. Upload the jar to artifactory, I see Vinod is having issues =
with that
>>>>> at
>>>>> the moment.
>>>>>=20
>>>>> Missing anything?
>>>>=20
>>>>=20
>>>=20
>>=20


--Apple-Mail=_A902249F-78F3-4A82-B370-BF9368D7A460--