reaperhulk/r509 — Issue #28: Update r509/version to x.ybeta (or something) while new dev is being done.
Author: justfalter
Created: 2012-01-03 17:35:44+00:00
State: open

If I build, at the moment, it still generates r509-0.5.gem ... it'd be good process to tag the release (ex: 0.5), and then update r509/version with the next projected release, maybe? 0.6beta, or something? It'd make it more clear to me if I want to compare functionality between a gem built off of HEAD and a release like 0.5 ...