Create a release about jzmq HOT 6 CLOSED

As I have said before: I am willing to create releases / tags, but I would need detailed, foolproof instructions on how to do it. In addition to that, we would have to agree on a policy (date based, sequential number, track 0mq) for the release names.

from jzmq.

I'd like to recommend git flow perhaps? I like it because it adds a structure to releases that is pretty easy to follow.

Basically it works like this:

• development work happens on the develop branch
• to work on a new feature, one types "git flow feature start snazzy-feature name"
  • this creates a new branch from develop for work on that specific feature
• finishing a feature is a matter of typing 'git flow feature finish' to merge the feature back into develop
• when you're ready to release, you run "git flow release start 1.5.0" which creates a release branch off develop for updating pom.xml and any other "pre-release activities"
• typing "git flow release finish" merges the release branch into master and creates a tag for the version.

I've been using this setup at work a lot (see http://blog.james-carr.org/2011/09/09/my-current-java-workflow/) and I think it would be a good setup to have periodic releases. :)

from jzmq.

Here are the steps to create a "release" on github using the tag/downloads.

1. Update the version in the pom.xml to the desired version and commit change
2. run command: "git tag v2.1.0"
3. Push the tags to the github repository using "git push --tags"

There should be a tag on the github repo in addition to a zip created in the downloads section.

I recommend using the latest as a release because it has been stable for me. We can postpone discussions on the full release policy in the future.

from jzmq.

We are discussing doing a release on issue #23, I suggest you comment on that issue. Thanks for the patience... Good luck.

from jzmq.

This should be able to be closed.

from jzmq.

Yes; @nathanmarz, can you please close this issue? Thanks.

from jzmq.