49e018be1e
* Add packages JSON file * Reformat document * Remove zlib * Remove 'Extra' concept * Add reference doc * Generate markdown * Add trailing CR * Apply suggestions from code review Co-authored-by: Matt Thalman <mthalman@microsoft.com> * Update schema per feedback * Remove commands property * Update markdown to commands schemea change * Add formats description * Change title * Add more examples * Add formats link to README * Apply suggestions from code review Co-authored-by: Matt Thalman <mthalman@microsoft.com> * Update schema with descriptions * Apply suggestions from code review Co-authored-by: Omair Majid <omajid@redhat.com> Co-authored-by: Noah Gilson <noahgilson@microsoft.com> * Rename files * Add eol-date * Update README files * Update schema links * Update link titles * Update per feedback * Update per feedback * Updates per feedback * Update description * Sort packages * Remove Debian 11 * Add min-version information * Change to link * Update markdown * Update schema per feedback * Apply suggestions from code review Co-authored-by: Matt Thalman <mthalman@microsoft.com> * Update markdown --------- Co-authored-by: Matt Thalman <mthalman@microsoft.com> Co-authored-by: Omair Majid <omajid@redhat.com> Co-authored-by: Noah Gilson <noahgilson@microsoft.com>
625 B
625 B
License information for release notes
Release notes include detailed information that may be useful in other forums or mediums, such as blogs, courses, or videos. The release notes are in markdown and JSON formats.
The dotnet/core repo uses the MIT license. You are free to use release note content under that license.
Some users may prefer a Creative Commons license. You may use release note content under the CC BY 4.0 license (with the same license holder as the MIT license).