Release Notes
Release notes describe the changes in a release, and the impact of those changes.
Release note fields:
caption- the plain version number (eg5.4.0)created- in DateFormatmodified- in DateFormatreleased- in DateFormat – only present if the release has been publishedtags- must includeReleaseNotestitle- the title of the release note (egRelease 5.4.0)description- a brief description of the releasetext- see below
The text of the release note should consist of the definition of a variable release-introduction followed by the invocation of the releasenote procedure. For example:
\define release-introduction()
Release v5.4.0 includes major improvements in a number of areas. See the [[project plan|https://github.com/orgs/TiddlyWiki/projects/4]] for more details.
\end release-introduction
<<releasenote 5.4.0>>Change Notes
Change notes describe a discrete change within a release. Change note fields:
title- by convention titles are formed$:/changenotes/<version>/<unique identifier>. The unique identifier is typically the primary GitHub PR or issue like#1234or a GitHub commit ID such as98f850609d29bc36ded83f90c0d5be231649254btags- must include$:/tags/ChangeNotechange-type- the type of change as a single string; see here for valid valueschange-category- the category of the change; see here for valid valuestext- full description of the changedescription- brief description of the changerelease- the release with which this change note is associated (eg5.4.0)github-links- a list of the GitHub links associated with this changegithub-contributors- a list of the GitHub handles of the developers responsible for the PR/commits
Impact Notes
Impact notes describe the impact of a particular change. There can be multiple impact notes for a given change.
Impact note fields:
title- by convention, the title of the associated change note with/deprecations/and a unique ID appended$:/changenotes/5.4.0/#8702/deprecations/darkmode-info-tiddlerchangenote- the title of the associated change notecreated- in DateFormatmodified- in DateFormattags- must include$:/tags/ImpactNotedescription- a brief description of the impactimpact-type- the type of impact; see here for valid valuestext- description of the impact if required