On 3/24/2018 5:45 AM, GitHub wrote: It turns out that one of the side effects of tag-in-stable-branch, that we clearly didn´t notice before, is that the master branch was still building packages in the v1.0 series that are < than stable branch. I think the same problem would apply when releasing/tagging from master and later on forking the tree, we just need to remember to tag master after stable fork + one commit (perhaps that should be part of the release process). Now that knet is slowly making its way into distributions, we need the master branch rpms/builds to be on higher versions to avoid confusion for package managements, CI and testing. v1.90 is pretty much random, but lower enough to give us space in future to have 1.9x Beta/RC1/RCx.. before a 2.0 GA. Cheers Fabio