On Tue, Apr 19, 2016 at 12:11:04PM -0700, Adam Williamson wrote:
I really think it would help if we use these terms carefully and precisely, and if we're going to re-define them in any way, make that clear and explicit.
Thanks Adam. I've been guilty of using them incorrectly (or at least sloppily) and will try to mend my ways.
This is probably mostly because "non-blocking" seems like it needs more explanation than "secondary" ("non-blocking" is generally a _good_ thing in software, right?). Also, it seems pretty tied to only what happens at release time, when really, what we want to say is "this is best-effort at release, and, if that release effort happens to go well, keeping it maintained is in a similar boat".
So, if we redefine anything, maybe "blocking" and "best-effort"? (I'm fine with "non-blocking" as a technical term... I'm just thinking about explaining it to people....)