-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
The idea is, the master branch would have the version of the next major release. Ie. the next target.
Eg. If the latest released version is 0.2.4 the master branch should be versioned 0.3.0.
Any minor release should be forked off of 0.2.4. Sometimes the minor/major specific changes might be intertwined. If a clean separation isn't possible, all the changes would be going out in the next major release.
A significant advantage of this is that the code on the master branch would be considered a different version on its own, and any packages depending on the master for development will be forced to take the new version into consideration.
This can wait until 0.3.1 is out. Post releasing 0.3.1 we can bump the version.
Metadata
Metadata
Assignees
Labels
No labels