Hi Abhishek, For almost every minor release we have, there is a cloud of uncertainty where nobody really knows when the release will be cut. Most of the time there is an email (or series of emails) that trigger the conversation of "are we now ready to cut a release?", where leads respond what backports are still pending, or if there are test suites that aren't really in the clear. For minor releases a mix of a time-based schedule with a set of each lead's group of passing tests, would be a nice way to predict when we can start having the conversation of cutting a release. It isn't a one-shot fix, but would certainly improve everyone who wants/needs a new release and can't get any clues as to what that may be. Something like: * Minor releases every 6 weeks * subset of test suites passing from each lead Would be a good way to start. If we can get that initial release path, it would be possible to start thinking about what "gating" really means for our releases (since we don't really have any sort of gating today) What do you think? -- 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
