tutor/CHANGELOG-nightly.md

# Changelog (nightly branch)

<!--
his changelog is for tracking changes made to the nightly branch (see:
https://docs.tutor.overhang.io/tutorials/nightly.html). The format of this file is identical
to the CHANGELOG.md file, except that there are not releases or "Unrelased sections. Entries
will be backported to the master branch at every major release.
When backporting changes to master, we should keep only the entries that correspond to user-
facing changes.
-->
docs: nightly development workflow 2021-09-28 16:38:22 +00:00			`# Changelog (nightly branch)`

docs: improve changelog to highlight 3rd party contributions With this change, we want to better highlight the contributions of developers to Tutor. We want to publicly acknowledge the positive impact that individuals and companies have on the development of the platform. to that end, each changelog entry can now be suffixed with the name of the author (individual or company) who authored the change. These names will find their way to the release notes for every release. Eventually, we also want to spread these release notes more widely. For instance, we could post new releases to the forum to notify the community of important changes. If you have contributed to Tutor in the past, feel free to open a PR and append your name to the changes that you made. We will not be able to update the release notes for every release out there, but your contributions will be acknowledged from the changelog. 2022-05-01 12:37:43 +00:00			`<!--`
			`his changelog is for tracking changes made to the nightly branch (see:`
			`https://docs.tutor.overhang.io/tutorials/nightly.html). The format of this file is identical`
			`to the CHANGELOG.md file, except that there are not releases or "Unrelased sections. Entries`
			`will be backported to the master branch at every major release.`
			`When backporting changes to master, we should keep only the entries that correspond to user-`
			`facing changes.`
			`-->`