Align licensing policy and attribution with the house standard
This commit is contained in:
@@ -2,7 +2,10 @@
|
||||
|
||||
**Base Policy Version:** 1.0
|
||||
|
||||
**Last Updated:** 2026-09-23
|
||||
**Last Updated:** 2026-09-26
|
||||
|
||||
The licensing-footer requirement incorporates upstream release policy v1.2;
|
||||
other release-workflow changes from that version are not adopted here.
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -135,6 +138,12 @@ canonical documentation for exact behavior. Every affected canonical document
|
||||
must be updated in the same candidate; a release note must not substitute for
|
||||
current documentation or defer required documentation changes.
|
||||
|
||||
Each new release note must end with the release navigation defined by the
|
||||
[OSS policy](oss.md#discoverability). Preserve those links on a hosted download
|
||||
page if one is used. The release procedure owns URL construction and channel
|
||||
treatment. This is ordinary preparation, not a new network check or approval
|
||||
gate; historical release notes are unchanged.
|
||||
|
||||
## Candidate Preparation And Validation
|
||||
|
||||
ConfigKit provides one local release checker. Run it once against the final
|
||||
|
||||
Reference in New Issue
Block a user