-
Notifications
You must be signed in to change notification settings - Fork 17
Description
- Pull Request: feat(rfc): Write RFC 0002 to propose specification extensions #58
- Discussion Thread(s):
Description
How Open Job Description Specifications should be versioned and released is something that has not been talked about. This RFC proposes a way to implement RFC functionality as Extensions without requiring a new Open Job Description Specification release.
Open Job Description Specification releases can be planned on a longer term schedule while still allowing RFC functionality to be implemented and tested in the meantime.
Roles
| Role | User |
|---|---|
| Proposed By | @Ahuge |
| Author(s) | @Ahuge |
Workflow
- Tracking issue created (label:
rfc/proposed) - RFC pull request submitted and ready for discussion (label:
rfc/exploring) - Last call for comments (labels:
rfc/exploringandrfc/final-comments) - Accepted and merged RFC pull request (label:
rfc/accepted-future) - Green-light for inclusion in a draft specification, and the author is creating and iterating on pull requests (label:
rfc/accepted-draft) - Pull requests are merged in to a draft specification (label:
rfc/accepted-staged) - Officially published in a non-draft revision of the specification (label:
rfc/released)
Please close this tracking issue when the proposal enters the Released stage of the process.
Open Points
For easier discovery, especially if there is a lot of discussion on this issue, then please keep this section updated
with brief summaries and pointers to the main points of discussion.
The author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue.