[GitHub] mesos pull request #259: Update contributors.yaml

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/259 ---

API Review Policy

Hi all, As BenM mentioned in a recent email, we discussed our process for review of API changes in the recent API working group meeting [1]. James Peach was also kind enough to share with me Apache Traffic Server's API review policy, which they have formalized [2]. I like the idea of putting our

Re: API Review Policy

+1 for keeping the policy in writing. Are we looking at the Traffic Server's API policy as a starting point for discussion? On Tue, Mar 13, 2018 at 10:12 AM, Greg Mann wrote: > Hi all, > As BenM mentioned in a recent email, we discussed our process for review of > API

Re: API Review Policy

Sure we can use that as a starting point. The basic policy that we discussed in the working group was that any public API change should be advertised on the developer mailing list. If no concerns are raised after several days, then the change could proceed. If concerns were raised, then discussion

Release policy and 1.6 release schedule

Hi folks, During the recent API working group meeting [1], we discussed the release schedule. This has been a recurring topic of discussion in the developer sync meetings, and while our official policy still specifies time-based releases at a bi-monthly cadence, in practice we tend to gate our

Re: API Review Policy

> On Mar 13, 2018, at 3:58 PM, Greg Mann wrote: > > Sure we can use that as a starting point. The basic policy that we > discussed in the working group was that any public API change should be > advertised on the developer mailing list. If no concerns are raised after >