+1 for time-based deprecation cycle of O(months)
On Mon, Sep 28, 2015 at 6:16 PM, Zameer Manji wrote:
> Niklas,
>
> Thanks for starting this thread. I think Mesos can best move forward if it
> switches from release based deprecation cycle to a time based deprecation
> cycle.
Only one binding vote on this release so far. Could I get another couple
votes, please?
On Thu, Sep 24, 2015 at 8:58 AM, haosdent wrote:
> Oh, got it. CentOS 6.6 don't have automake 1.4, so have to build it for
> source code. I fetch it from
>
Hi everyone,
With a (targeted) release cadence of *one month*, we should revisit our
deprecation cycles of 3 releases (e.g. in version N, we warn. In version
N+1, support both old and new API. In Version N+2, we break compatibility).
Sometimes we cannot do the first step, and we deprecate in
+1 (binding), tested on internal CI
On Thu, Sep 24, 2015 at 8:58 AM, haosdent wrote:
> Oh, got it. CentOS 6.6 don't have automake 1.4, so have to build it for
> source code. I fetch it from
> https://git-wip-us.apache.org/repos/asf/mesos.git before.
>
> On Thu, Sep 24, 2015
+ Dev
On Mon, Sep 28, 2015 at 1:56 PM, Dave Lester wrote:
> Can this be discussed on the mailing list? Thanks
>
>
> On Monday, September 28, 2015, Joseph Wu wrote:
>
>> + Niq, Joris, MPark (so that this doesn't get neglected when the website
>> is
Thanks in advance !
Best,MandeepĀ