+1 to 0.10.0 as well. The increased release overhead and fragmented feature exposure is something I'd rather avoid. I think having a consistent and credible release story on Aurora side outweighs the benefits of chasing after Mesos release cadence. Moving forward, with Mesos 1.0.0 I believe we will have less to worry about as Mesos would have to comply with semver guidelines and plan breaking API changes around major version bumps.
On Mon, Oct 5, 2015 at 4:44 PM, Joshua Cohen <[email protected]> wrote: > +1 to releasing as 0.10.0. > > I hope that Mesos does move to a time-based deprecation cycle rather than > +/- 1 version, since it could easily be the case that a Mesos release falls > at a time when we are not prepared to release Aurora. Perhaps until Mesos > addresses their deprecation cycles, we make official our informal policy > that all new features are gated behind a command line flag such that we > feel comfortable releasing a new version from any commit on master? > > On Mon, Oct 5, 2015 at 4:24 PM, Kevin Sweeney <[email protected]> wrote: > >> It seems that this is not a correct usage of semver and that we should >> release the link to 0.23.0 as 0.10.0. Given the mesos deprecation cycle >> described in that ticket, 0.22.0 would be compatible with 0.21.0. IMO a >> patch release should never break compatibility with versions that the >> previous patch version worked with - it should be for things like >> showstopper security or reliability bugs. >> >> I'd be +1 to releasing a 0.10.0 that contains only the patch changing our >> link target to 0.23.0 and pushing our next "feature release" to 0.11.0. >> >> On Mon, Oct 5, 2015 at 3:49 PM Zameer Manji <[email protected]> wrote: >> >> > Hey, >> > >> > As I brought up on today's IRC meeting >> > <http://markmail.org/message/2v7224yhnkichnze> we have a bit of a >> problem >> > in AURORA-1503 <https://issues.apache.org/jira/browse/AURORA-1503> and >> > some >> > discussion is required to figure out what we need to do. >> > >> > Since Aurora 0.9.0 was released the Mesos release cadence has increased >> to >> > about one a month, while keeping their deprecation policy to be -1/+1. >> > Aurora 0.9.0 was released against Mesos 0.22 which means Aurora 0.9.0 >> will >> > work against Mesos 0.23 but not Mesos 0.24. >> > >> > The scenario means our users are not able to update to Mesos 0.24 (or >> > later) if they are running Aurora 0.9.0. The deprecation policy also >> means >> > we also need to carefully think about which versions of Mesos we release >> > against. >> > >> > I'm proposing we do the following: >> > >> > - Release 0.9.1 which is 0.9.0 linked against Mesos 0.23. This will >> > allow our users to upgrade their clusters to Mesos 0.24 in the short >> > term. >> > Mesos 0.23 is also compatible with Mesos 0.22 meaning existing users >> > should >> > not be impacted. >> > - Assuming we do the above, we release the next major version of >> Aurora >> > against Mesos 0.24. This provides a smooth upgrade path from 0.9.x to >> > 0.10.x. >> > >> > What are our thoughts on this? >> > >> > -- >> > Zameer Manji >> > >>
