Topic on Talk:Code stewardship

Under "Base Service Level Agreements", how is "non-production" defined? Two examples coming to my mind: Beta features to be promoted to stable at some point? Support in MW Core for database backends which are not used on Wikimedia servers?

Also, the Priority values (?) imply that someone would have to both regularly and quickly (for UBN/High: less than a week) set the "Priority" field in every task, while I'd say that some teams pretty much ignore the Priority field and prefer for example workboard columns to express planning/urgency of tasks.

Originally the idea of "production" vs "non-production" was focused on whether the code in question was being used in WMF production. We could use "Beta" as a flag for this provided Beta code is isolated and does not impact non-beta code. However, as the application of the stewardship model gets applied beyond WMF, it probably doesn't make sense to include that in a base SLA definition. In fact, I don't know at this point if a base service level agreement event makes sense. As WMF, we may get to a point where we share a common base SLA, but I don't think we'll be there for a while.

As for priority values, this goes back to the discussion about how to differentiate between different tasks, especially those that are bugs. Not all bugs/tasks are created equally :-) Provided that we are able to effectively differentiate between tasks/bugs, it'll probably make sense to commit to/or at least target some level of responsiveness.

All that being said, it may not even make sense to define SLAs for bugs/tasks. It just initially seemed like a natural extension to SLAs for Code Reviews.