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
In its current state the version number field allows any characters to be input - http://bigbite.im/i/8pjF2S
What is your proposed solution?
Given that the version number should follow semantic versioning (MAJOR.MINOR.PATCH) numbering, I am suggesting the following features be implemented to:
Sanitise the field so it only accepts numbers.
Only allow the release note to be published once it the version number is input and in the correct format.
(optional) Have it so the version number increments on the previous number.
(optional) UI/UX change to the field so that it is 3 fields for each number instead of 1 field - http://bigbite.im/i/gNDeta (crude mock up)
The text was updated successfully, but these errors were encountered:
What problem does this address?
In its current state the version number field allows any characters to be input - http://bigbite.im/i/8pjF2S
What is your proposed solution?
Given that the version number should follow semantic versioning (MAJOR.MINOR.PATCH) numbering, I am suggesting the following features be implemented to:
The text was updated successfully, but these errors were encountered: