Review Draft publication schedule

[annevk]

To spread Review Draft publication we have taken our current list of standards (15), divided it by 3, and publish the resulting sets (assuming there have been changes) with one-month intervals. How does this change as we add standards?

One approach could be that we keep the maximum for a month at 5, which means we need to revisit things if the list gets to 30. If this seems reasonable, is it okay if standards end up slightly shifting when they get published as they end up in a different set? (They're in lexicographical order at the moment.)

(This question came up as I've been thinking about automating pull request creation for Review Drafts and ideally I'd use db.json as the source of what to publish.)

[othermaciej]

The Workstream Policy doesn't say much about this except "approximately every 6 months". Anything that meets these criteria is ok. Sticking at 5 per month until we have 6 equal groups seems reasonable. If it's useful to record the schedule in db.json, with no effect on its other outputs, that seems ok to me.

[foolip]

Assigning each standard two months during each year when review drafts should be published in db.json sounds good. When we create new standards, we can just pick two months that make the first instance not too soon, and that doesn't put too many at the same time.

[foolip]

@annevk would you like to prepare a PR encoding the months into db.json? (I could work on it if you have no such intention.)

[annevk]

@foolip yeah, I'd be happy to work on that, probably tomorrow. Anyone want to bikeshed on rd_months?

[foolip]

I have some affinity for something with "schedule" in the name since that's the CI terminology this would map to if we automate. So review_draft_schedule or rd_schedule are colors of the bikeshed I'd like.