Re: Problems with deprecation cycles for critical/hard to adapt dependencies

+1 to Timothy's proposal. Here is a concrete example that can guide the policy. Aurora 0.9.0 was released in July 2015 and was built against Mesos 0.22. At the time, I don't think anyone was aware that 0.24 would come out in September 2015 and break compatibility with with 0.22 w.r.t

Re: Problems with deprecation cycles for critical/hard to adapt dependencies

Hi Zameer, thanks for comments - I'd be happy to help the Aurora team upgrade to support Mesos 0.24+ I'll follow up on the issue you pointed us to. *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Thu, Oct 1, 2015 at 10:29 AM, Zameer Manji

Re: Problems with deprecation cycles for critical/hard to adapt dependencies

@vinod, ben, jie - Any thoughts on this? I am in favor of the time based deprecation as well and can come up with a proposal, taken there are no objections. Niklas On 28 September 2015 at 21:09, James DeFelice wrote: > +1 for time-based deprecation cycle of O(months)

Re: Problems with deprecation cycles for critical/hard to adapt dependencies

I think besides changing to time based, we should provide a lot more visibility of the features that we are starting to deprecate, and I think each release we can also highlight the remaining releases/time each feature remaining lifetime so users are reminded on each release the full list they

Re: Problems with deprecation cycles for critical/hard to adapt dependencies

+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.