Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Tue, Mar 22, 2016 at 5:10 AM, Kevin Klues wrote: > This way it's easy to track the full set of release candidates, as well as > how they relate to previous release candidates, minor releases, and point > releases. There is no essential difference with the current approach

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Fri, Mar 18, 2016 at 4:59 PM, Kevin Klues wrote: > I respectfully disagree. > > The whole purpose of tags is to mark permanent things like releases, > whereas branches are designed as temporary lines of development that > come and go (and grow and shrink) dynamically all the

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

The way I've dealt with this on other projects in the past is the following: 1) RC1s for minor releases (e.g., 0.28.0-rc1, 0.29.0-rc1, 0.30-rc1, etc.) are *always* tagged at some commit on the master branch. ​ This is only true for actual minor release (i.e. not point releases, e.g. 0.28.1,

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

+1 for branch per RC (if we go with branches). I like your argument against re-writing history if we make a mistake. I think the 2 issues that have come up are: 1) visibility into the release process 2) pain / lack of context for the release manager of backports to resolve merge conflicts for

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

A single branch for a release seems brittle because it assumes that RC tag N shares the same lineage as RC tag N-1. This is mostly true, but not always. The branching approach that would mirror how I've put together releases would be to have a branch for each RC. The RC N branch is usually on top

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

The SHAs rarely exist on HEAD because we tend to cherry-pick bug fixes into release candidates. I'm all for using branches in the repository to put together the release candidates, as well as have committers consider their bug fixes for some N number of backport (future LTS) releases. As Kevin

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Wed, Mar 16, 2016 at 11:56 AM, Joseph Wu wrote: > Cong Wang, > > The tags are sync'd. See: https://github.com/apache/mesos/releases > > You might not have done: git pull --tags Yeah, I figured it out by myself too. This is why I hate tags personally, branches are

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Wed, Mar 16, 2016 at 11:49 AM, Cong Wang <cw...@twopensource.com> wrote: > On Mon, Mar 7, 2016 at 8:29 PM, Michael Park <mp...@apache.org> wrote: >> Please find the release at: >> https://dist.apache.org/repos/dist/release/mesos/0.27.2 >> >> It is

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

I like the idea of using branches to manage releases. We can use that to manage point releases and backports as well. Say we want to cut 0.29.0 now, we fork a branch 0.29.0 and tag RCs in that branch. Once the RC is accepted, the head of that branch will become the release. Then, we immediate

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

> > Please find the release at: > > https://dist.apache.org/repos/dist/release/mesos/0.27.2 > > > > It is recommended to use a mirror to download the release: > > http://www.apache.org/dyn/closer.cgi > > > > The CHANGELOG for the release is available at: > > >

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Mon, Mar 7, 2016 at 8:29 PM, Michael Park <mp...@apache.org> wrote: > Please find the release at: > https://dist.apache.org/repos/dist/release/mesos/0.27.2 > > It is recommended to use a mirror to download the release: > http://www.apache.org/dyn/closer.cgi > > Th

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

I agree with Kevin -- tags are immutable, so they're naturally suited for labeling releases, which ought to be immutable too. On Fri, Mar 18, 2016 at 4:59 PM, Kevin Klues wrote: > I respectfully disagree. > > The whole purpose of tags is to mark permanent things like releases,

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

I respectfully disagree. The whole purpose of tags is to mark permanent things like releases, whereas branches are designed as temporary lines of development that come and go (and grow and shrink) dynamically all the time. On Fri, Mar 18, 2016 at 4:04 PM, Jie Yu wrote: > I

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

BTW, if the tag is created against a commit that *doesn't* become "unreachable" from HEAD [1], then `git pull` is sufficient to also pull down the tags. The only time I've needed to do `git fetch --tags` is when the tagged commit SHA gets merged away. So presumably the process being followed by

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

@team, are we going to provide LTS version? If so, we definitely need a branch to back merge issues; if not, we release a new version monthly (??), we'd suggest user to upgrade to next release. Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Technology, STG, IBM

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

The Mesosphere deb/rpm packages are available here: http://open.mesosphere.com/downloads/mesos/ On 7 March 2016 at 23:29, Michael Park <mp...@apache.org> wrote: > Hi all, > > The vote for Mesos 0.27.2 (rc1) has passed with the > following vote

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

mp...@apache.org >> > > >> > >> > wrote: >> > >> > >>> > >> > >> > >>> > > Vinod, we've

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

gt; > > > >> > >>> > >> I don't see CHANGELOGs for these versions on the master > branch? > >> > >>> > >> > >> > >>> > >> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway < > >> > neil.con

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

d (briefly) in the release emails, 0.27.2, 0.26.1, >> > >>> > >> > 0.25.1, >> > >>> > >> > and 0.24.2 contains a new feature: "reliable floating poi

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

; >>> > >> > To elaborate on that slightly, Mesos now only supports scalar > > >>> >

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

> > > >>> > >> > To elaborate on that slightly, Mesos now only supports scalar > >>> > >> > resource > >>> > >> > values with three decimal digits of precision (e.g., reserving > >>> > >> > &qu

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

> >> > fine-grained resource values (> 3 decimal digits of precision), >> > >> > that >> > >> > will no longer be suppor

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

ay see slightly different results; >>> > >> > furthermore, if any frameworks were trying to manage extremely >>> > >> > fine-grained resource values (> 3 decimal digits of precision), >>> > >> > that >>> > >> >

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

>> > > > https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E > > >> > > > >> > > > >> > > > https://docs.google.com/document/d/14qLxjZsfIpfy

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

x/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E > >> > > >> > > >> > https://docs.google.com/document/d/14qL

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E >> > >> > >> https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing >> > https://issues.apache.org/jira/browse/

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

il > > > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park <mcyp...@gmail.com> wrote: > > Hi all, > > > > Please vote on releasing the following candidate as Apache Mesos 0.27.2. > > > > > > 0.27.2 includes the following: > > >

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

/issues.apache.org/jira/browse/MESOS-4687 Neil On Fri, Feb 26, 2016 at 8:54 PM, Michael Park <mcyp...@gmail.com> wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.27.

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

> amd64/centos/7 > amd64/debian/jessie > amd64/ubuntu/precise > amd64/ubuntu/trusty > amd64/ubuntu/vivid > > Kapil > > > On Fri, Feb 26, 2016 at 11:54 PM, Michael Park <mcyp...@gmail.com> wr

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

te on releasing the following candidate as Apache Mesos 0.27.2. > > > 0.27.2 includes the following: > > > >- MESOS-4693 <https://issues.apache.org/jira/browse/MESOS-4693>

[VOTE] Release Apache Mesos 0.27.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.27.2. 0.27.2 includes the following: - MESOS-4693 <https://issues.apache.org/jira/browse/MESOS-4693> - Variable sha

Re: Mesos 0.27.2

+1 Thanks for catching this issue and managing the release. On Wed, Feb 24, 2016 at 2:15 AM, Michael Park wrote: > Today we ran into another backwards compatibility issue in master the > `/state` endpoint in 0.27.1. Since 0.27.1 has already been shipped, I would > like to

Mesos 0.27.2

Today we ran into another backwards compatibility issue in master the `/state` endpoint in 0.27.1. Since 0.27.1 has already been shipped, I would like to propose to cut a 0.27.2. The JIRA ticket is MESOS-4754 , and r43937