How do force the next version up? about gitversion

[andreasohlund]

Talked this through with @SimonCropp during our gym session this morning:) and we haven't solved this yet.

The only thing that comes to mind is a tag on develop with a known name, "start-next-major" or similar?

I don't like a tag since that clutters the "releases" on github with useless cruft so if anyone has a better algorithm I'm all for it!!

Side note:

In theory it would work with just keep on working since when you create a release-{nextmajor}.0.0 branch it would be correctly versioned and when you merge to master develop would jump to {nextmajor}.1.0. This has the big caveat that during the release of {nextmajor}.0.0 the develop branch will still be stuck in a lower version , {currentmajor}.{currentminor+1}.0 which would be very confusing.

[JakeGinnivan]

The way GitHubFlowVersion does it is it looks for a file in the root of the repo called NextVersion.txt, if that file exists, and the version is higher than the computed version then it takes precedence.

That way a pull request can bump the major/minor and when it gets merged the SemVer of the CI automatically bumps.

[andreasohlund]

That would work. That said I'd really would want to avoid adding uneeded
files to the repo is possible. How about some special keyword/syntax in the
commit message?

git commit -m "I had to change the api [BreakingChange]"

or

git commit -m "I had to change the api [BumpMajor]"

With the above we don't need a file and you can still bump from a pull by
marking it a breaking change?

Thoughts?

On Wed, Jan 8, 2014 at 10:47 PM, Jake Ginnivan [email protected]:

The way GitHubFlowVersion does it is it looks for a file in the root of
the repo called NextVersion.txt, if that file exists, and the version is
higher than the computed version then it takes precedence.

That way a pull request can bump the major/minor and when it gets merged
the SemVer of the CI automatically bumps.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/66#issuecomment-31876238
.

[JakeGinnivan]

That would be better for a few reasons:

• No additional files
• If both [BreakingChange] and [MinorChange] are present or multiple [MinorChange]/[BreakingChange], we simply bump the major semver by 1. Means two people bumping major between releases will not be a problem

It could also tie into the release notes and be a keyword that it could pickup as additional metadata about the change?

[andreasohlund]

It could also tie into the release notes and be a keyword that it could pickup as additional metadata about the change?

Definitely, though arguable there should be an issue for that commit tagged with "breaking change" or similar?

[andreasohlund]

Now we just have to trick @nulltoken to wave his magical lib2git wand to make all this happen? :)

[JakeGinnivan]

True, may not know if it is breaking or just major until you get to implementing the issue.

I have code in GitReleaseNotes which scans commit messages for regexes already (it finds issue numbers then cross references against closed issues since last tag)

I'm happy to pick this up once #60 is pulled in, because this is required for the transition to GitVersion anyways :)

[nulltoken]

Now we just have to trick @nulltoken to wave his magical lib2git wand to make all this happen? :)

@JakeGinnivan I was about to answer "Yes", but it looks like you've been faster than me 😉 Please, let me know if I can help you with anything

[JakeGinnivan]

@nulltoken review #60 :) need feedback as it changes a bunch of stuff around GitFlowVersion's SemVer classes

[JakeGinnivan]

The GitHubFlow side supports NextVersion.txt, if everyone is happy with that approach, we can make it available for both GitFlow and GitHubFlow then close off this issue?

[andreasohlund]

Not a big fan of adding text files but I'd say this is definitely one of the valid strategies for NextVersion we should support!

[JakeGinnivan]

We need to add documentation for NextVersion.txt, then close this issue.

We could also open another issue to add support for bumping via commit messages?

Breaking: I broke stuff bumps major

Feature: New thing bumps minor?

[andreasohlund]

+1 one on a new issue just to track it at least

On Sun, Mar 30, 2014 at 8:01 PM, Jake Ginnivan [email protected]:

We need to add documentation for NextVersion.txt, then close this issue.

We could also open another issue to add support for bumping via commit
messages?

Breaking: I broke stuff bumps major

Feature: New thing bumps minor?

Reply to this email directly or view it on GitHubhttps://github.com//issues/66#issuecomment-39033450
.

[JakeGinnivan]

#137 is tracking