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
With the latest release of 1.1.1 and a 1.2-wip branch already being worked on it seems like moving forward a tag should be created for all stable releases when they are phased out. This way developers who have yet to upgrade or feel they can not upgrade (for what ever reason) will be able to review docs and can find their stable version. Also, it will provide better history, bug tracking, etc as the framework evolves.
Ideally we would have a tag for each stable release <major>.<minor>.<patch>, but if that becomes obnoxious it would be nice to at least have a tag for <major>.<minor>.<last_patch>
The text was updated successfully, but these errors were encountered:
The build script does have the --release flag which will create a tag based on the version. I think we just need to make sure to do that when releasing a new version.
It probably wouldn't be bad to go back and tag the previous releases as well.
With the latest release of 1.1.1 and a 1.2-wip branch already being worked on it seems like moving forward a tag should be created for all stable releases when they are phased out. This way developers who have yet to upgrade or feel they can not upgrade (for what ever reason) will be able to review docs and can find their stable version. Also, it will provide better history, bug tracking, etc as the framework evolves.
Ideally we would have a tag for each stable release
<major>.<minor>.<patch>
, but if that becomes obnoxious it would be nice to at least have a tag for<major>.<minor>.<last_patch>
The text was updated successfully, but these errors were encountered: