Reflections on publishing process for continuous improvement

Please note process things we can continue to improve that will make for a better publication process the next time we make a release. Please add your name to the list so we can ask for further detail…

• When making the numbered release spaces and branches, ensure that only release-specific changes go into that space/branch until we are in final stages of release. Normal work can continue in Development. — @Rachel Lawson (Unlicensed)

• Communication is key. We alerted people to the creation on branches/spaces via PC & TC meetings and alerts in the #General channel in Slack but not everyone is seeing these

  • Consider how we ensure notes from meetings are read by ALL bb leads and distributed to their teams — @Rachel Lawson (Unlicensed)

  • Consider removing inter-Slack links and requiring everyone to be connected to the actual GovStack Slack directly, otherwise they cannot see important channels like #general etc — @Rachel Lawson (Unlicensed)

• Follow up on https://github.com/orgs/GitbookIO/discussions/38 — @Rachel Lawson (Unlicensed)

• Ensure the template is being followed in BB Specs (the technical writer will help with this).

• Commitment to deadlines: BB Specs would ideally be finished within 2 weeks of anticipation of the release deadline so that finalized content can be reviewed and re-formatted without it being a work in progress during the same period.

•