As we’re now into the full throes of the 4.8 cycle, the uncertainty that comes with not releasing “until it’s ready” inevitably creates a lull in areas other than the three focuses. Areas like maintaining our inline documentation, which populates the official Code Reference.
In the past, the freshness of core’s inline documentation relied almost entirely on a regular, major release schedule. And due to a preference for keeping the number of changed files low, inclusion of docs fixes in minor releases has previously been a rare occurrence.
I’ve spoken with @matt, and the decision has been made to go ahead and prioritize some inline docs fixes for inclusion in minor releases going forward.
As with any decision, there are certainly pros and cons. Here are some of them:
- Ability to continue our ongoing inline docs maintenance adjacent to the 4.8 major release
- Ability to address some glaring docs errors that we’ve been fixing manually in the Code Reference
- Prioritize docs improvements for existing functionality in the three focus areas ahead of the 4.8 release, freeing up resources for documenting new functionality
- Number of changes and changed files in minor releases will increase (within reason)
- All changes pushed to trunk will also need to be backported to the 4.7 (or current stable) branch
It’s worth noting that the reason the number of changed files has traditionally been kept low is to reduce the number of automatic update failures. The hope is that since we’ve been pushing automatic updates for 10 major versions now, reliability is less of a factor now than it has been previously.
It’s also worth noting that we shouldn’t expect a downtick in activity for core team resources focused on the three areas following this decision. As always, inline docs contributors will be focused on major release priorities before minor release ones.
This decision simply maintains the inline docs team’s ability to ensure the usefulness of core’s source documentation for the thousands of users and developers who rely on it every day.
#inline-docs, #minor-releases, #release-process
The release process is complex and beyond one person. Releasing is an intricate dance that we haven’t been sufficiently capturing. Knowledge siloed in heads needs to be committed to public, institutional memory. The upcoming 4.5 release is an opportunity to capture every step of the dance so that we can iterate process, automate away lingering drudgery, and improve our cognitive net for the stressful task of releasing to 25%. I like using checklists in this cognitive net. They relieve anxiety, make process transparent, and help teams flow during stress. We already have a couple release checklists. We can build on those while adopting a little checklist culture in a manner empathetic to developers and flow. Pitch:
Checklist cool tricks
- distribute power.
- push power of decision making to the periphery.
- provide a cognitive net.
- make the minimum necessary steps explicit.
- make sure simple steps are not missed.
- make sure people talk.
- capture and shape real flow.
- inspire flow in emergencies and sustain it through the quotidian.
- capture flow between teams.
- encourage a shared culture around flow.
- accessibly capture institutional memory in the context of flow.
Attributes of a good checklist
What makes a good checklist? Checklist shouldn’t be about just checking boxes. Instead of being a chore and an admonishing finger, checklists should fit and assist real flow. The Checklist Manifesto offers these suggestions. Ideally, checklists…
- are not lengthy.
- have clear, concise objectives.
- define a clear pause point at which the checklist is supposed to be used.
- have fewer than ten items per pause point.
- fit the flow of the work.
- continually update as living documents.
See this checklist for checklists and this example checklist for more.
Stuff to checklist
The major release checklist attempts to use pause points and follow the suggestions above. The major and minor release checklists are pretty rough and incomplete and overlap with each other. These and the things to keep in mind list need love and unification with help from developers who are in the release flow and handling controls on the release train.
about.php is…quite the process. It needs the oxygenating powers of a checklist.
Checklist Feature plugin merges.
Checklist bundled theme releases so stuff like this makes it into institutional memory.
Beta and RC releases.
Plenty of other stuff. 🙂
Start by capturing. As we walk 4.5 release flows, capture.
Selected quotes from The Checklist Manifesto
Checklists supply a set of checks to ensure the stupid but critical stuff is not overlooked, and they supply another set of checks to ensure people talk and coordinate and accept responsibility while nonetheless being left the power to manage the nuances and unpredictabilities the best they know how.