by lazy consensus: if anyone does NOT like the idea of a six
> release deprecation period (~six months), please speak up soon.
> Otherwise, I'll writeup a docs page that has our release/deprecation
> policy (MESOS-3995).
>
> Neil
>
> On Thu, Nov 19, 2015 at 6:32 PM, Marco Ma
wise, I'll writeup a docs page that has our release/deprecation
policy (MESOS-3995).
Neil
On Thu, Nov 19, 2015 at 6:32 PM, Marco Massenzio <ma...@mesosphere.io> wrote:
> Thanks, Neil, for getting the ball rolling on the matter.
>
> Absolutely in favor of extending the deprecation
Thanks, Neil, for getting the ball rolling on the matter.
Absolutely in favor of extending the deprecation cycle of features to make
framework developers' and operators' lives easier.
However,
-1 for extending compatibility up to N - 6
1) this prevents us to innovate and introduce functionality
Folks,
In the last community sync, we briefly discussed Mesos release policy.
In particular, we talked about the current cadence of ~monthly
releases and how that relates to (a) deprecation periods (b) support
for running a "mixed version" cluster.
As I understand it, the current policy is as
