Adopt the standard OSS attribution policy
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Release Policy
|
||||
|
||||
**Base Policy Version:** 1.1
|
||||
**Base Policy Version:** 1.2
|
||||
|
||||
**Last Updated:** 2026-09-26
|
||||
|
||||
@@ -80,12 +80,11 @@ instructions. Keep the note proportionate to the change. Fixed sections and
|
||||
explicit no-action boilerplate are not required. Existing historical notes
|
||||
need not be rewritten to adopt this format.
|
||||
|
||||
End each new release note with a `LICENSE | ATTRIBUTION` footer. Both links
|
||||
must be absolute URLs to files at that release's immutable Scriptorium tag:
|
||||
the root `LICENSE` and `docs/oss/attribution.md`, respectively. The checked-in
|
||||
note remains the source of the hosted release body, so this footer reaches the
|
||||
hosted page without a separately maintained notice. Do not retrofit published
|
||||
notes.
|
||||
Include the release footer defined by the [OSS policy](oss.md#discoverability)
|
||||
in each new release document and preserve it on the hosted download page. The
|
||||
release procedure defines the concrete URLs and publication mechanics. Prepare
|
||||
these links with the release note; they do not add a network check or approval
|
||||
gate.
|
||||
|
||||
Keep exact current contracts in their canonical documents and update affected
|
||||
documentation with the behavior change. Link to those documents from the note
|
||||
|
||||
Reference in New Issue
Block a user