Release life cycle fields #57
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
How can I preview this? Is preview supported? The vercel thingie looks pretty empty. |
I asked @lfrancke about Vercel too since I never used it and I have no access to it. But yes, that would be the preferred way to review. |
|
Looks good, except that I think there should be an LTS true/false field too. |
| name String | ||
| general_availability DateTime? | ||
| released Boolean | ||
| end_of_development DateTime? |
There was a problem hiding this comment.
I don't think all of these really apply to us....you took them from some document I sent to you, right?
There was a problem hiding this comment.
I looked through the proposed OpenEoX schema and I don't think a conclusion has been reached yet.
Maybe for now we only want to add a field for end of life?
Also: Could you explain why we have two fields released/general availability? Not sure I understand the difference.
There was a problem hiding this comment.
@soenkeliebau in case you have input
There was a problem hiding this comment.
general_availability says when a release has/will become generally available. This is to help communications in advance and document actions in the future.
released is flag that is to be turned on on the date (or not in case foreseen events).
| name String | ||
| general_availability DateTime? | ||
| released Boolean | ||
| end_of_development DateTime? |
There was a problem hiding this comment.
I looked through the proposed OpenEoX schema and I don't think a conclusion has been reached yet.
Maybe for now we only want to add a field for end of life?
Also: Could you explain why we have two fields released/general availability? Not sure I understand the difference.
Fixes stackabletech/issues#496