<Reducing this to ceph-devel/ceph-maintainers, this discussion doesn't need to blast all over> On Wed, Aug 16, 2017 at 5:13 AM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: > On Tue, Aug 15, 2017 at 10:35 PM, Matt Benjamin <mbenjami@xxxxxxxxxx> wrote: >> I think we need a v12.1.5 including #17040 > > *I* think that this is getting to a point where we should just have > nightly development releases. > > What is the benefit of waiting for each RC every two weeks (or so) otherwise? RC releases are supposed to be release candidates, as in, things that we think could be the release. As with much else in the Luminous cycle that broke down a bit, and that's frequently not really the case because we know it's missing features we want to make available, but in general it's not too far off — we believe the code is stable; it's passing our nightlies; we want people to test and use it a lot more rigorously than dev checkpoints. Every RC is practice for the real thing and making them available the same way as real releases is part of that. > > On one side we are treating the RC releases somewhat like normal > releases, with proper announcements, waiting for > QA suites to complete, and have leads "ack" when their components are > good enough. But on the other side of things > we then try to cut releases to include fixes as immediate as possible > (and as often as that means) > > We've had 3 releases already in August and this would mean discussing > a *fourth*. We had 12.1.2 on August 2 and 12.1.3 on August 9. This last 12.1.4 was an emergency because we broke things, and that'll happen sometimes no matter what dev process you're using. Let's not jump overboard just because we had one emergency and another idle suggestion that it'd be nice to fix bug X. If your concern is that these builds take a lot of time, I'm sure we'd all love a smoother build infrastructure. But build time is not the dominating issue when deciding how we do releases when we want users to practice with them. :) -Greg > >> >> Matt >> >> On Tue, Aug 15, 2017 at 5:16 PM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: >>> On Tue, Aug 15, 2017 at 2:05 PM, Abhishek <abhishek@xxxxxxxx> wrote: >>>> This is the fifth release candidate for Luminous, the next long term >>>> stable release. We’ve had to do this release as there was a bug in >>>> the previous RC, which affected upgrades to Luminous.[1] >>> >>> In particular, this will fix things for those of you who upgraded from >>> Jewel or a previous RC and saw OSDs crash instantly on boot. We had an >>> oversight in dealing with another bug. (Standard disclaimer: this was >>> a logic error that resulted in no data changes. There were no >>> durability implications — not that that helps much when you can't read >>> your data out again.) >>> >>> Sorry guys! >>> -Greg >>> >>>> >>>> Please note that this is still a *release candidate* and >>>> not the final release, we're expecting the final Luminous release in >>>> a week's time, meanwhile, testing and feedback is very much welcom. >>>> >>>> Ceph Luminous (v12.2.0) will be the foundation for the next long-term >>>> stable release series. There have been major changes since Kraken >>>> (v11.2.z) and Jewel (v10.2.z), and the upgrade process is non-trivial. >>>> Please read these release notes carefully. Full details and changelog at >>>> http://ceph.com/releases/v12-1-4-luminous-rc-released/ >>>> >>>> Notable Changes from 12.1.3 >>>> --------------------------- >>>> * core: Wip 20985 divergent handling luminous (issue#20985, pr#17001, Greg >>>> Farnum) >>>> * qa/tasks/thrashosds-health.yaml: ignore MON_DOWN (issue#20910, pr#17003, >>>> Sage Weil) >>>> * crush, mon: fix weight set vs crush device classes (issue#20939, Sage >>>> Weil) >>>> >>>> >>>> Getting Ceph >>>> ------------ >>>> * Git at git://github.com/ceph/ceph.git >>>> * Tarball at http://download.ceph.com/tarballs/ceph-12.1.4.tar.gz >>>> * For packages, see http://docs.ceph.com/docs/master/install/get-packages/ >>>> * For ceph-deploy, see >>>> http://docs.ceph.com/docs/master/install/install-ceph-deploy >>>> * Release sha1: a5f84b37668fc8e03165aaf5cbb380c78e4deba4 >>>> >>>> [1]: http://tracker.ceph.com/issues/20985 >>>> >>>> >>>> Best Regards >>>> Abhishek >>>> >>>> _______________________________________________ >>>> 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 >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
