Gameplan!

[IDisposable]

Where we are now

We're currently so far diverged from the origin upstream that it's getting more reasonable to adopt our own strategies for future releases. As it stands now, the master branch is serving as the version 2 release chain.

The current release for v2 is v2.13.1 v2.14.0 on NPM which is nearing end of life, there's some breaking changes to simplify life coming in v3 so I'm planning on just doing maintenance-only fixes there. We may be able to backport some stuff, but I suspect we're going to stop at v2.14 or so.

The v3 release chain is just getting started, but hopefully will point out of release candidate mode sooner. Before we do that, I want to cut over to master over to for the v3 chain, and rename that branch as well (to main). We left it alone before of a vain hope of back-porting to @Taysen version, but I think it's safe to say that is neve going to happen.

Also in the works, I've got a PR on CDNJS repo to get the NPM package releases automatically pulled into CDNJS so jsfiddles are easier to create.

Overarching plan

1. Merge Work on table padding issue #95 #104 into the master
2. Create a v2-tracking branch from that
3. Cut a release from v2-tracking to v2.14.0
4. Push that to npm as the current release for v2.x
5. Merge v3.0.0-rc1 into master
6. [ ] Rebase Cleanup node cloning and skip sandbox #103 onto main created a hand merge... too much churn
7. Merge Cleanup node cloning and skip sandbox #103 into master
8. Cut another v3 release candidate See
9. Push that to npm as the release candidate for v3
10. Consider merging Add support for Shadow DOM (ShadowRoot) #101 and/or Filter out sandbox iframe from clone tree #102 after rebasing them on master
11. Rename master to main
12. PROFIT

[IDisposable]

We now have two tracking branches... master (soon to be main) will be the v3 branch until we go to v4 (if ever). The v2.x branch is tracking the v2 versions until we put v3 out as general version (and thereafter used for backporting hot fixes if needed).

All releases are tagged with their version number and there's a corresponding GitHub release for them as well.

[IDisposable]

Merged ShadowDom changes (but needs some help) and renamed branches