Hi everyone, We talked a bit about this during the CLT meeting this morning. How about the following proposal: - Target release date of Mar 1 each year. - Target freeze in Dec. That will allow us to use the holidays to do a lot of testing when the lab infrastructure tends to be somewhat idle. If we get an early build out at the point of the freeze (or even earlier), perhaps this capture some of the time that the retailers have during their lockdown to identify structural issues with release. It is probably better to do more of this testing at this point in the cycle so that we have time to properly fix any big issues (like performance or scaling regressions). It is of course a challenge to motivate testing on something that is too far from the final a release, but we can try. This avoids an abbreviated octopus cycle, and avoids placing August (which also often has people out for vacations) right in the middle of the lead-up to the freeze. Thoughts? sage On Wed, 26 Jun 2019, Sage Weil wrote: > On Wed, 26 Jun 2019, Alfonso Martinez Hidalgo wrote: > > I think March is a good idea. > > Spring had a slight edge over fall in the twitter poll (for whatever > that's worth). I see the appeal for fall when it comes to down time for > retailers, but as a practical matter for Octopus specifically, a target of > say October means freezing in August, which means we only have 2 > more months of development time. I'm worried that will turn Octopus > in another weak (aka lightly adopted) release. > > March would mean freezing in January again, which would give us July to > Dec... 6 more months. > > sage > > > > > > > On Tue, Jun 25, 2019 at 4:32 PM Alfredo Deza <adeza@xxxxxxxxxx> 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. > > > > > > > > > > > On Mon, Jun 17, 2019 at 12:22 PM Sage Weil <sage@xxxxxxxxxxxx> wrote: > > > >> > > > >> On Wed, 5 Jun 2019, Sage Weil wrote: > > > >> > That brings us to an important decision: what time of year should we > > > >> > release? Once we pick the timing, we'll be releasing at that time > > > *every > > > >> > year* for each release (barring another schedule shift, which we want > > > to > > > >> > avoid), so let's choose carefully! > > > >> > > > >> I've put up a twitter poll: > > > >> > > > >> https://twitter.com/liewegas/status/1140655233430970369 > > > >> > > > >> Thanks! > > > >> sage > > > >> _______________________________________________ > > > >> ceph-users mailing list > > > >> ceph-users@xxxxxxxxxxxxxx > > > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > > > > > _______________________________________________ > > > > ceph-users mailing list > > > > ceph-users@xxxxxxxxxxxxxx > > > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > > > > > > -- > > > > Alfonso Martínez > > > > Senior Software Engineer, Ceph Storage > > > > Red Hat <https://www.redhat.com> > > <https://red.ht/sig> > >
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
