Precedence of tag and branch names when deducing version

[pi3k14]

I think you should tune the rules for calculating version numbers a bit.

When a commit is a tip of branch and contains a tag, the tag should only have precedence if it equals the version number of the branch and contains som extra metadata (eg. 1.0.0-rc.3), or if the branch doesn't contain any version number.

Eg. develop branch is just updated and tagged with an alpha/beta number, then there is forked a release branch with a given version number. An initial build from the release branch will create a version number from the tag, since the commit are the same.

I can't se any use case where current functionality makes sense.

[asbjornu]

If you could provide this as a (failing) RepositoryFixture test in a pull request, it would be much easier to understand what behavior you want as well as fix it. If you're able to fix your issue in the same pull request, it would be even better. 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

[pi3k14]

@asbjornu could you have a look at this (to re-open the issue)?

[asbjornu]

@pi3k14, if you could follow up #1348 (comment), we can perhaps move this forward. In its current state, there's not much I can do, sorry.

[pi3k14]

@asbjornu not quit sure I follow you on

if you could follow up #1348 (comment)

#1743 is my first attempt to describe the issue as a test case.

[asbjornu]

Sorry, @pi3k14. I did not notice the existence of #1743 until you pointed it out now. The test looks good. If you have ideas on how to fix it, feel free to expand the PR.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

[arturcic]

Closed by #1743