Re: [DISCUSS] Branching for a release soon?

[Jim Apple <jb...@cloudera.com>]

That might be the place for release candidates. I added KEYS to
https://dist.apache.org/repos/dist/release/incubator/impala/KEYS now,
following http://incubator.apache.org/guides/releasemanagement.html

On Wed, Aug 31, 2016 at 4:37 PM, Jim Apple <jb...@cloudera.com> wrote:
> Thanks, Tom!
>
> I have added my key to
> https://dist.apache.org/repos/dist/dev/incubator/impala/KEYS.
>
> Committers who are interested in acting as release managers at some
> point might be interested in getting keys, joining the apache web of
> trust, putting the keys on home.apache.org, etc. The instructions for
> all of this can be found by poking around the apache web space. Here
> is a reasonable place to start:
> http://www.apache.org/dev/release-signing.html
>
> On Wed, Aug 31, 2016 at 3:39 AM, Tom White <to...@cloudera.com> wrote:
>> On Wed, Aug 31, 2016 at 12:07 AM, Jim Apple <jb...@cloudera.com> wrote:
>>> Testing is passing. I am waiting on the following commits to land in
>>> master, though, before I cherry-pick them to branch-2.7.0:
>>>
>>> https://gerrit.cloudera.org/#/c/3995/
>>> https://gerrit.cloudera.org/#/c/3937/
>>> https://gerrit.cloudera.org/#/c/3936/
>>> https://gerrit.cloudera.org/#/c/4160/
>>>
>>> These are all intellectual property / branding changes, but they are
>>> all things that I think the IPMC may require of a release:
>>>
>>> 1. A copyright audit
>>>
>>> 2. Java package changes away from cloudera
>>
>> Strictly speaking this is not necessary for the first incubator
>> release, but it's good to do early if possible.
>>
>>>
>>> 3. Incubating DISCLAIMER file
>>>
>>> Once these are committed and in 2.7.0, I will re-test and make a
>>> release candidate tarball. I think the next steps are to
>>> cryptographically sign it, put it in my home.apache.org web space,
>>
>> Release candidates should go in a directory under
>> https://dist.apache.org/repos/dist/dev/incubator/, then once they have
>> been approved they can be moved to the final location with a single
>> commit.
>>
>> See http://www.apache.org/dev/release.html#stage.
>>
>> Tom
>>
>>> then ask PMC members to download it, build it, test it, and vote on
>>> it.
>>>
>>>
>>> On Mon, Aug 29, 2016 at 10:02 AM, Jim Apple <jb...@cloudera.com> wrote:
>>>> #1 is now done.
>>>>
>>>> I am now doing #2, making the branch and starting testing. Expect
>>>> possible churn on this since this is our first attempt at cutting an
>>>> upstream release.
>>>>
>>>> On Fri, Aug 19, 2016 at 8:40 AM, Jim Apple <jb...@cloudera.com> wrote:
>>>>> I would like to volunteer to be the next release manager for an
>>>>> upcoming Apache Impala 2.7 (incubating) release. I plan to:
>>>>>
>>>>> 1. Get a vote done adding to our bylaws the procedure for creating a
>>>>> branch. (See thread from yesterday)
>>>>>
>>>>> 2. Create a release branch, possibly backdated a few commits from HEAD
>>>>> to a commit that looks stable.
>>>>>
>>>>> 3. Maintain that branch by cherry-picking bugfix commits from "master"
>>>>> as necessary to get the tests running cleanly.
>>>>>
>>>>> 4. Make a release candidate and call for a vote here, then on the IPMC
>>>>> list (which is required for Incubator releases)
>>>>>
>>>>> Obviously, this glosses over some details about publishing and signing
>>>>> releases, but I would welcome feedback on this outline.