You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming v1.1.0 update we need to start tracking changes between releases of the AsciiDoc port of Hugo Book.
We could either add a "Changes" section in the main README or create an independent CHANGELOG.md document; the former solution seems better to start off with, and when the list becomes long we could then move it to the independent CHANGELOG.md document.
Create a CHANGELOG label to track issues relating to updating the ChangeLog.
As for the details of the changes list, we could the list brief by providing reference links to the various Issues and commits, and just keep a brief resume in the text description.
The text was updated successfully, but these errors were encountered:
in main README doc:
* Add new "Changelog" section (see #58).
* In "Acknowledgements" section, credit Roody Yogurt, Nikos Chantziaras
and Juhana Leinonen for the annotated Hugo Book PDF (see #57).
* Update release badge to v1.1.0 (see #68).
With the upcoming v1.1.0 update we need to start tracking changes between releases of the AsciiDoc port of Hugo Book.
We could either add a "Changes" section in the main README or create an independent
CHANGELOG.md
document; the former solution seems better to start off with, and when the list becomes long we could then move it to the independentCHANGELOG.md
document.CHANGELOG
label to track issues relating to updating the ChangeLog.README.md
a "Changes" section:As for the details of the changes list, we could the list brief by providing reference links to the various Issues and commits, and just keep a brief resume in the text description.
The text was updated successfully, but these errors were encountered: