Next steps for the library

[WilliamKelley]

Had a discussion yesterday with the Marketplace team where i advocated for progressing with breaking implementations over discussing until an agreeable path is determined (see above thread). My thinking was that I'd prefer PDS to make progress and us reconcile changes to make them less breaking or improve the upgrade experience, rather than see no implementation progress.

To aid in this, i suggested they could maintain a separate branch (like next) that publishes advanced versions or a different package. IMPORTANTLY, this is the option where progress is made with NO regard to easing breaking changes. If instead regard IS given and a large enough change batch is covered, then they can be merged to main. Going with the former and just merging of mature next version eventually to cover the batch condition is probably how it will play out.

I think advanced packages versions are the better choice in the case, with format 1.0.0-alpha.0 which would progress in the last digit. I've come to see that uses alpha versions over 0.x.x versions is a bit more widely used and respected because it doesn't induce the false implication for the reader that there are strictly fix-versions or non-breaking feature/fix versions.

The order of operations for breaking changes are

• new "next" typography/palette for PDS v2
  • separate __next__* vars until next step completed
• update components styles to PDS v2
• replace typog/palette

Then the order of remaining things are arbitrary in comparison

• release v1 stable??
• upgrade to MUI v5
  -possibly internalize dependency
• break out package renamings
  • namings tbd: @prenda/pds-js-foundations, @prenda/pds-react-components, etc.