Skip to content

Commit

Permalink
add (all?) the steps for building a release
Browse files Browse the repository at this point in the history
  • Loading branch information
fetep committed May 22, 2011
1 parent 5b6d425 commit dfe253a
Showing 1 changed file with 24 additions and 0 deletions.
24 changes: 24 additions & 0 deletions docs/release-engineering.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,27 @@ I do not suspect the 'x' (currently 1) will change frequently. It should only ch
if there are major, backwards-incompatible changes made to logstash, and I'm
trying to not make those changes, so logstash should forever be at 1.y,z,
right? ;)

# building a release.

* Make sure all tests pass
** rake ???
* Update VERSION.rb
* Update docs/learn.md
* Ensure CHANGELOG is up-to-date
* git tag v$VERSION
* git push origin master
* Build binaries
** rake package:gem
** rake package:monolith:jar
** rake package:monolith:tar
* rake docs output=../logstash.github.com/docs/$VERSION
** Note: you will need to use c-ruby for this
* cd ../logstash.github.com
** git add docs/$VERSION
** git commit -m "version $VERSION docs" && git push origin master
* Publish binaries
** Stage binaries at <tt>carrera.databits.net:/home/jls/s/files/logstash/
** rake gem:publish
* Update #logstash IRC /topic
* Send announcement email to logstash-users@, include relevant download URLs & changelog (see past emails for a template)

0 comments on commit dfe253a

Please sign in to comment.