The v2.0 issue

[mor10]

Picking up where #121 left off:

The purpose of this issue is to decide which features go into WP Rig v2.0.

Some rules:

• v1.0.x is now considered legacy. Only bugfixes and Gutenberg updates will be applied to this branch.
• v1.1 branch is deprecated and will be removed in due time.
• The focus of v2.0 will be refactoring the build and development process. What that means is what's discussed in this issue.
• Other feature additions beyond Gutenberg (moving target) will be punted to v2.1 or later. This includes CSS refactoring, SVG sprites, etc.
• v1.0.x will remain master until v2.0 is ready. Obviously.

Have at it!

[felixarntz]

Do I understand correctly that you plan to move master to a v1.0 branch before we merge v2.0 into master? I'm in favor of that, then we can easily backport some fixes that affect both, and thus still maintain v1.

[mor10]

Yes.