Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMHxVREyAw+27BJu4i0KBeK5CKDF1EY5vfvUoo8PSDR4BrJMDg@mail.gmail.com>
References: <CANntcz6wb=smZ6g75wJHzzGzStOynLrHt300WAdDTw8L9Wd-Gg@mail.gmail.com>
 <CAMHxVREyAw+27BJu4i0KBeK5CKDF1EY5vfvUoo8PSDR4BrJMDg@mail.gmail.com>
From: Jie Yu <yujie.jay@gmail.com>
Date: Tue, 11 Apr 2017 16:52:32 -0700
Message-ID: <CAMHxVRGHn7-CrzN9TvC_sd2uFh3jU0c+xinZC5oAuy7Y2E-z2w@mail.gmail.com>
Subject: Re: 1.0.4 release
To: dev <dev@mesos.apache.org>
Content-Type: multipart/alternative; boundary=001a114fd7cc124eb3054cecc976
archived-at: Tue, 11 Apr 2017 23:52:43 -0000

--001a114fd7cc124eb3054cecc976
Content-Type: text/plain; charset=UTF-8

Also, looks like 1.0.3 is still showing "unreleased" in JIRA.

On Tue, Apr 11, 2017 at 4:51 PM, Jie Yu <yujie.jay@gmail.com> wrote:

> Thanks Vinod. This sounds good.
>
> I don't see any additional patch on top of 1.0.3, at least in the
> changelog. Can you make sure to update the changelog for that? (or you
> forgot to update the master changelog?)
>
> - Jie
>
> On Tue, Apr 11, 2017 at 12:33 PM, Vinod Kone <vinodkone@apache.org> wrote:
>
>> Hi folks,
>>
>> Though, we are technically past the 6 month support period for the 1.0.x
>> series, there were some commits that were cherry-picked onto the 1.0.x
>> branch after 1.0.3 was released. So, I'm willing to do a 1.0.4 patch
>> release which will be the last patch release for 1.0.
>>
>> I plan to cut an RC later this week, so if you have things that must
>> absolutely go to the technically unsupported 1.0.x branch, please cherry
>> pick them ASAP. If you are still on 1.0.x, please upgrade to 1.1.x or
>> 1.2.x
>> which are still officially supported.
>>
>> Thanks,
>> Vinod
>>
>> P.S: I'm planning to delete the 1.0.x branch after 1.0.4 release to
>> strongly signal the EOL for 1.0.x and to avoid committers mistakenly
>> backporting fixes to 1.0.x. Any objections?
>>
>
>

--001a114fd7cc124eb3054cecc976--