-
Notifications
You must be signed in to change notification settings - Fork 59
Bud Release Process
neilconway edited this page Aug 21, 2012
·
10 revisions
To make a new release of the Bud gem, do the following:
- Ensure you test your changes with both MRI 1.8 and 1.9.
- If needed, update the version number in
bud.gemspec
and commit. - If needed, update the release notes in
History.txt
, including noting the date associated with the new release. - Create a tag for the release and push it to Github:
$ git tag -a v0.MAJOR.MINOR
$ git push --tags
- Build a gem and push it to RubyGems:
$ gem build bud.gemspec
$ gem push bud-0.MAJOR.MINOR.gem
(Note that you'll need the appropriate credentials at RubyGems.)
4. Bump the version number in bud.gemspec
(to reflect the development sources) and create a new section in History.txt
, commit and push.
5. Email bloom-lang@googlegroups.com
with a brief release announcement, and update the website accordingly.