Replies: 5 comments
-
But... Our changelog really isn't md. |
Beta Was this translation helpful? Give feedback.
-
True, it's not currently real markdown, but it is close. |
Beta Was this translation helpful? Give feedback.
-
It's rather unclear how to implement this request: Where do we point these links on master, so that the only step required on a release is to replace the links?! |
Beta Was this translation helpful? Give feedback.
-
My point on the previous post is that we already have a tremendous list of documents which need to be (manually) adjusted when a new release branch is being created. I'm very much against creating more manual steps in the process to create a new release branch. |
Beta Was this translation helpful? Give feedback.
-
Somewhere on the "info" screen shown on successful login we should add a prominent link to the changelog.
This can be done reasonably easily by pointing at one of
Use of information from
Should allow us to add section links (a TOC) to the top of the Changelog file making navigation to individual versions easier for the user.
The viewing experience for the user can be further enhanced by renaming
Changelog
toChangelog.md
so that github renders the content as markdown automaticallyAdding this may assist users to decide if they want to immediately upgrade, or defer until the next release.
This should probably be done in the 1.7 series so it's available to users considering upgrading to 1.8 when that's released later this year
Beta Was this translation helpful? Give feedback.
All reactions