Replies: 4 comments 7 replies
-
I know you say basically this in the next paragraph, so… Is this necessary to plan for? If there were an S1 update, couldn't we fork from the latest S1-based commit to a branch at that point, make the change and release it in the 12.x.x lifecycle? |
Beta Was this translation helpful? Give feedback.
-
I think you mean this but just to be clear with the previous section, we're saying there will be no new S1 components or features, but we reserve the right to do—however unlikely—minor updates to the system. |
Beta Was this translation helpful? Give feedback.
-
|
Also, this change would impact the Spectrum Token Visualizer because it only shows the data in the |
Beta Was this translation helpful? Give feedback.
-
Assuming this means you're planning a v14 for these changes? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem statement
Spectrum 2 data will be published as Spectrum Tokens v13.0.0, as discussed in this other RFC. At that time, the data currently in the
mainbranch, released as Spectrum Tokens v12.x.x, won't have any planned releases with feature updates. However, it is expected that some platforms, implementations, and products won't be able to switch over to Spectrum Tokens v13 immediately. This RFC is designed to discuss the plans for supporting S1 for those products after S2 graduates frombeta.History
Previous related RFCs:
Proposal
What will and won't be included in the S2 GA release?
Included:
betabranchNot included:
distdirectory format outputThese changes would result in breaking changes to the token output format and work to update the implementation parsers. It's planned to be completed using RFCs, snapshot/beta releases for partner vetting after S2 GA is released.
What types of changes should be expected, and who decides?
main/latest.How will releases be made?
We can keep an
s1-legacybranch with the last of the S1 release's data that can be used for any releases needed. It would be expected to be released under the v12 version number.Even if we don't have a branch with the
s1data, we can still checkout the git tag from the last v12.x.x release and provide the release that way.Consequences or Required Actions
Any product still using an S1 version won't receive any new component or system features.
Unresolved questions
Timeline
We'll keep this RFC open for comment until Monday, March 10, 2025.
We are planning to graduate from the
betabranch to themainbranch as described above on Thursday, March 13, 2025.Beta Was this translation helpful? Give feedback.
All reactions