Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research and determine scope of v12 #16221

Open
Tracked by #15803
tay1orjones opened this issue Apr 17, 2024 · 3 comments
Open
Tracked by #15803

Research and determine scope of v12 #16221

tay1orjones opened this issue Apr 17, 2024 · 3 comments
Labels
planning: umbrella Umbrella issues, surfaced in Projects views role: design ✏️ role: dev 🤖 version: 12 Issues pertaining to a future major release of Carbon

Comments

@tay1orjones
Copy link
Member

tay1orjones commented Apr 17, 2024

Determine what we want to include in v12 (to keep things

  • code comments (todo v12, remove in v12?, etc.)
  • existing ideas in v12 #15803
  • deprecated items (light prop, etc)
  • what are we going to promote to stable? enable-v12-overflowmenu, "OverflowMenuV2"
  • gather a list of all these, run a prioritization exercise with everyone, potentially use some of these attributes for signal:
    • How valuable is the change for consumers?
    • How valuable is the change for maintainers? (the Carbon team)
    • How disruptive is this change?
    • How much effort does the change require?
    • ... each of the above attributes needs a scale defined - how do you define "low" disruption vs "high" disruption, for instance?
  • Design-focused items:
    • ...

Solicit feedback on the plan via a playback of these findings and exercises to:

  • the greater Carbon team
  • the Carbon ecosystem - other internal/external framework authors, PAL library maintainers, strategic products, interested parties (previous "release partners"?)
    • Determine a plan for we intend to begin coordination of the v12 changeset with strategic library partners (@carbon/web-components, @carbon/ibm-products, carbon-components-angular, carbon-components-svelte) - ideally before the first prerelease?

Announce the plan

  • Could potentially coincide with Deprecate end-of-support v10 assets #12494. The timelines match up for end of Q3 2024 or beginning of Q4 2024, which would also be 1 year from when we intend to ship the first v12 prerelease

Audit the v12 items to determine migration steps for each, if we should codemod, etc.

@tay1orjones tay1orjones mentioned this issue Apr 17, 2024
@tay1orjones tay1orjones added version: 12 Issues pertaining to a future major release of Carbon role: dev 🤖 role: design ✏️ labels Apr 17, 2024
@tay1orjones tay1orjones moved this to ⏱ Backlog in Design System Apr 17, 2024
@tay1orjones tay1orjones moved this from ⏱ Backlog to 🪆 Needs Refined in Design System Apr 18, 2024
@tay1orjones tay1orjones added this to the 2024 Q3 milestone May 21, 2024
@sstrubberg
Copy link
Member

What about the kits? How are we going to handle the change management between majors as it relates to the kits?

@sstrubberg
Copy link
Member

sstrubberg commented Jun 24, 2024

v11 chopping block

#7538

@sstrubberg
Copy link
Member

Use this as an opportunity to drop support for things. Themes?

@sstrubberg sstrubberg added the planning: umbrella Umbrella issues, surfaced in Projects views label Jun 27, 2024
@github-project-automation github-project-automation bot moved this to Triage in Roadmap Sep 11, 2024
@sstrubberg sstrubberg moved this from Triage to Icebox 🧊 in Roadmap Sep 11, 2024
@sstrubberg sstrubberg removed this from the 2024 Q3 milestone Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planning: umbrella Umbrella issues, surfaced in Projects views role: design ✏️ role: dev 🤖 version: 12 Issues pertaining to a future major release of Carbon
Projects
Status: Later 🧊
Development

No branches or pull requests

2 participants