[New Feature]: Reduce Version Explosion

[wphyojpl]

Checked for duplicates

Have you checked for duplicate issue tickets?

Yes - I've already checked

Alternatives considered

Have you considered alternative solutions to your feature request?

Yes - and alternatives don't suffice

Related problems

Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets.

Currently, every PR bumps a version depending on major, minor, or bug.

It ends up increasing many versions in 1 release.
This is done so that the "release" tab is not ovewritten before a release.

But each release has a jump in version.

Describe the feature request

• Instead of bumping the real version in PR merges, append another version.
• Example: Just after a fresh release, the version is 17.3.1.
• When a PR is created as a feature, it will become 17.3.1D0.1.0
• When another PR is created as a bug, it will become 17.3.1D0.1.1
• and so on..
• When it finally releases, it will choose the largest non 0 after D to increase the real version
• Example: 17.3.1D0.4.6 where it has 4 new features and 6 bugfixes, it becomes 17.4.0
• Example: 17.3.1D1.0.6 where it has 1 breaking change and 6 bugfixes, it becomes 18.0.0