netlify[bot]
commented
5 months ago Deploy Preview for playful-gelato-7892ba ready!
| Name | Link |
|---|---|
| Latest commit | 57f6a49a80616f9062291d3c69eb3e8414875dc5 |
| Latest deploy log | https://app.netlify.com/sites/playful-gelato-7892ba/deploys/65b8c68b3a0fea00084880dc |
| Deploy Preview | https://deploy-preview-70--playful-gelato-7892ba.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This PR adds a blueprint guideline regarding automated blog posts for new releases of packages. This change follows on the discussions in https://github.com/epiverse-trace/epiverse-trace.github.io/issues/135, where it became clear that a guideline can provide clarity. Inviting the original participants of the discussion for sharing their thoughts :-)
This PR explicates that patch release blogs are not a necessity, but are possible at the discretion of the code owner. This helps unburden those who may feel like it is a necessity, but also gives flexibility for the code owners of the package to make the final call (context matters).
Scenario
I can imagine the scenario where a patch is for a critical vulnerability may require an urgent update to our community in the form of a blog. It also gives guidance to team members that they are not required to release a blog for patches.
Next steps
Given this is a small change that will not substantively change the immediate situation, I will move ahead if no objections arise before end of the week.