You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason I'm thinking about this, is, if someone has an old project and something isn't working, or, if someone has an old project and they want to get new features, we don't want to break their old project.
Version using semantic versioning or some scheme where the primary version number is upgraded only when breaking changes are introduced. So Version 3.0, 3.2, 3.4.2, etc are all backwards compatible to any version before within the 3.0 release.
Then, someone could "pick" the version of the items they want to target. In the future this would allow us to target upgrades for standard elements and forms components without breaking things.
It would also lead nicely into the future ability to "upgrade" forms component install without creating a fresh project and manually moving gumx files around.
The text was updated successfully, but these errors were encountered:
Look into versioning the objects.
The reason I'm thinking about this, is, if someone has an old project and something isn't working, or, if someone has an old project and they want to get new features, we don't want to break their old project.
Version using semantic versioning or some scheme where the primary version number is upgraded only when breaking changes are introduced. So Version 3.0, 3.2, 3.4.2, etc are all backwards compatible to any version before within the 3.0 release.
Then, someone could "pick" the version of the items they want to target. In the future this would allow us to target upgrades for standard elements and forms components without breaking things.
It would also lead nicely into the future ability to "upgrade" forms component install without creating a fresh project and manually moving gumx files around.
The text was updated successfully, but these errors were encountered: