buildar 0.0.3.1 → 0.0.4.1

data/MANIFEST.txt

@@ -1,4 +1,3 @@
 MANIFEST.txt
 VERSION
-README.md
 rakefile.rb

data/VERSION

@@ -1 +1 @@
-0.0.3.1
+0.0.4.1

data/rakefile.rb

@@ -123,6 +123,7 @@ task :gitpush do
   # may prompt
   sh "git push origin"
   # this kills the automation
+  # use key-based auth?
   # consider a timeout?
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: buildar
 version: !ruby/object:Gem::Version
-  version: 0.0.3.1
+  version: 0.0.4.1
   prerelease: 
 platform: ruby
 authors:
@@ -51,7 +51,6 @@ extra_rdoc_files: []
 files:
 - MANIFEST.txt
 - VERSION
-- README.md
 - rakefile.rb
 homepage: http://FIX.COM/
 licenses:

data/README.md

@@ -1,29 +0,0 @@
-Buildar
-=======
-Buildar is a set of Rakefile methods and tasks to help automate versioning,
-packaging, releasing, and publishing ruby gems.
-
-Rake tasks
-----------
-* version - show the current project version (./VERSION)
-* manifest - show the files tracked by the gem (./MANIFEST.txt)
-* tag - git tag according to current version, pushed to origin
-* bump_build - increment the 4th version number (1.2.3.4 -> 1.2.3.5)
-* bump_patch - increment the 3rd version number (1.2.3.4 -> 1.2.4.0)
-* bump_minor - increment the 2nd version number (1.2.3.4 -> 1.3.0.0)
-* bump_major - increment the 1st version number (1.2.3.4 -> 2.0.0.0)
-* build - bump_build, build a .gem file inside pkg/
-* publish - gem push
-* release - build, tag, publish
-* release_patch - bump_patch, release
-* release_minor - bump_minor, release
-* release_major - bump_major, release
-
-Philosophy
-----------
-* Track the release version in one place: ./VERSION
-* The version only matters in the context of a release.  For internal development, git SHAs vastly outclass version numbers.
-* "The right version number" for the next release is a function of the current release version and the magnitude (or breakiness) of the change
-* http://semver.org/
-* Automate everything
-* This does not absolve you from attentending to changelogs, etc.