-
Notifications
You must be signed in to change notification settings - Fork 41
SEP 33: Re-adding point zero to major Salt versions - process update #49
Conversation
Hello! Thank you for submitting a Salt Enhancement Proposal! Our process is detailed in the README.md and more about the SEP Life-cycle. An Open Core Team member will be assigned to follow up and help guide this SEP soon and you will find the this in the Community Slack channel #sep. |
👍 salt-bootstrap needs to be fixed as well, to handle pinning to major versions. Some time ago I added a kludge for that: saltstack/salt-bootstrap#1491 |
It's unclear. Are you proposing to go back and re-release e.g. 3000 as 3000.0? If so, this could be even more disruptive. Un-releasing 3000 isn't really possible, and I'm sure there's at least one system that will treat 3000 and 3000.0 as different. More in-depth impact analysis is required. If not, then it just makes things even more inconsistent. You can't put the genies of bad decisions back in the bottle once you've released them. |
I didn't intent to go back and update already released versions; however, if there is a reason to re-release I would be willing to discuss, but I did write it as to suggest as such. I can adjust. The intent of this proposal is add it back in as part of the process or standard operating procedure and to detail the decision going forward to include the point zero specifically because without it we have deviated from it and it causes many problems. I can include more details in the SEP. |
updated language to answer the TBD question of re-releasing - at this time we do not see a benefit
Adding a draft SEP to re-add the point zero to major Salt versions as a standard operating procedure or to the process.
####.#
example:3005.0
and once approved the date at which this will become the standard will be announced/communicated