pre release identifier - keep & bump

[salzig]

Added the option to bump pre.
1.2.3 -> 1.2.3-alpha
1.2.3-alpha -> 1.2.3-beta
1.2.3-beta -> 1.2.3-rc

bump major and bump minor will reset pre release identifier
to nothing.
I would prefer 'alpha', opinions?

[grosser]

what I usually see is 1.2.3.alpha not -alpha (e.g. rails)

[grosser]

to dry it up maybe reuse PRERELEASE -> #{PRERELEASE.compact.join("|")}

[salzig]

SemVer names '-' as separator for prerelease- and '+' for build- identifier.
gem versionomy handels many different formats.
Hard to say what's the "right way" to do it.

[grosser]

rake just went 0.9.3.beta.1https://rubygems.org/gems/rake/versions/0.9.3.beta.1
:D
I definitely like SemVer as a standard, and as long as it works with
rubygems (aka I can install --pre) then it does not really matter :)

On Sun, Oct 21, 2012 at 8:52 AM, Ben notifications@github.com wrote:

In lib/bump.rb:

 OPTIONS = BUMPS | ["current"]

• VERSION_REGEX = /(\d+.\d+.\d+)/
• VERSION_REGEX = /(\d+.\d+.\d+(?:-(?:alpha|beta|rc))?)/

SemVer http://semver.org/ names '-' as separator for prerelease- and
'+' for build- identifier.
gem versionomy https://github.com/dazuma/versionomy handels many
different formats.
Hard to say what's the "right way" to do it.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/11/files#r1898754.

[salzig]

"The version string can contain numbers and periods, such as 1.0.0. A gem is a ‘prerelease’ gem if the version has a letter in it, such as 1.0.0.pre." - RubyGems Specification

also good to know RationalVersioningPolicy and Summary

[gregorym]

@salzig Can you add documentation to the README plz.