Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Team:Architecture
Description
As all releases, also the 17.0.1 patch release shall have a corresponding document. However, having a full detailed release note like a major release, it is excessive, since we are just fixing one issue.
My suggestion is to create a subsection inside the major 17.0 release note page.
Attachments
Issue Links
Activity
OK, I draft the changes on a ticket branch based on 17.0.x pipelines branch.
I have added a short text in the thicket branch and created a PR to merge it to the 17.0.x branch:
https://github.com/lsst/pipelines_lsst_io/pull/125
From a release management point of view this is sufficient, however, I suppose that Simon Krughoff or John Swinbank may want to make it more clear.
I suggested a slightly different wording from what Jonathan suggested, but either way is fine.
Thank you Simon.
Jonathan Sick, I have merged this ticket branch in 17.0.x. The patch release is already available. Please feel free to merge the relevant parts into master in order to include the patch information in the main pipelines page.
I think that's fine to do for 17.0.1
I do think a lot of aspects of the release notes for pipelines.lsst.io (and by extension, other major products) need an overhaul. As the documentation engineer for pipelines.lsst.io, I'll be proposing a new system. But for now, I think your subsection approach is fine.