You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the work on CLE is progressing it would be useful to add an externalReference type to hold a link to a CLE, OpenEOX or other kind of document that describes the versioning/support policy of the project.
Possible solutions
Naming is certainly the most difficult problem, but the new type might be called support-lifecycle or simply lifecycle.
Currently there is no machine-readable format to describe EOS/EOL data, but the link could point to a human-readable page.
The text was updated successfully, but these errors were encountered:
could you open a PR targeting the 1.7-dev branch, and propose the needed changes you have in mind?
FYI: the topic is currently in stage "proposal". A working implementation/spec via pull-request would set it to "prototyp".
When you are happy with your prototype, you can request to have it moved to "draft" - at this stage the community is asked to vote/comment the feature/implementation - and after 4 weeks the votes are counted and future steps might happen.
Describe the feature
While the work on CLE is progressing it would be useful to add an
externalReference
type to hold a link to a CLE, OpenEOX or other kind of document that describes the versioning/support policy of the project.Possible solutions
Naming is certainly the most difficult problem, but the new type might be called
support-lifecycle
or simplylifecycle
.Currently there is no machine-readable format to describe EOS/EOL data, but the link could point to a human-readable page.
The text was updated successfully, but these errors were encountered: