Figure out major release versioning strategy for v9

[ling1726]

Split from #19106

Details are in RFC #19658 but will be extracted into its own RFC for a long running discussion on how to version vNext packages.

• Independent versioning strategy
• Lockstep (full vs major lockstep)

[msft-fluent-ui-bot]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.

[layershifter]

We have now #23914 that covers it. Should be this closed?

[ling1726]

I don't think this is the same actually, we still don't really know how we are going to do our first breaking change

[Hotell]

I don't think this is the same actually, we still don't really know how we are going to do our first breaking change

IMO this issue should be named differently. if i understood it correctly we need a strategy how will we approach v10 per say.

regarding v9 as @layershifter mentioned we have #23914 .

WDYT @ling1726 ?

[ling1726]

@Hotell is it incorrectly named ? this isn't about release but about versioning.

[msft-fluent-ui-bot]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.