On Tue, 25 Jun 2019, Alfredo Deza wrote: > On Mon, Jun 17, 2019 at 4:09 PM David Turner <drakonstein@xxxxxxxxx> wrote: > > > > This was a little long to respond with on Twitter, so I thought I'd share my thoughts here. I love the idea of a 12 month cadence. I like October because admins aren't upgrading production within the first few months of a new release. It gives it plenty of time to be stable for the OS distros as well as giving admins something low-key to work on over the holidays with testing the new releases in stage/QA. > > October sounds ideal, but in reality, we haven't been able to release > right on time as long as I can remember. Realistically, if we set > October, we are probably going to get into November/December. > > For example, Nautilus was set to release in February and we got it out > late in late March (Almost April) > > Would love to see more of a discussion around solving the problem of > releasing when we say we are going to - so that we can then choose > what the cadence is. I think the "on time" part is solveable. We should just use the amount of time between take the previous release's freeze date and the target release date and go with that. It is a bit fuzzy because I left it up to the leads how they handle the freeze, but I think mid-Januaray is about right (in reality we waiting longer than that for lots of RADOS stuff). v14.2.0 was Mar 18, so ~2 months. The cadence is really separate from that, though: even if every release were 2 full months late, if we start with the same target it's still a 1 year cycle. sage _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |