Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: released v1.0 via github #150

Merged
merged 1 commit into from
Feb 2, 2016
Merged

Problem: released v1.0 via github #150

merged 1 commit into from
Feb 2, 2016

Conversation

hintjens
Copy link
Member

@hintjens hintjens commented Feb 2, 2016

After a release we must always update the working version number
so that anyone using it does not confuse it with the released code.

Solution: update project version to 1.1

After a release we must always update the working version number
so that anyone using it does not confuse it with the released code.

Solution: update project version to 1.1
c-rack added a commit that referenced this pull request Feb 2, 2016
@c-rack c-rack merged commit b0adf90 into zeromq:master Feb 2, 2016
@hintjens
Copy link
Member Author

hintjens commented Feb 2, 2016

@zeromq/malamute-maintainers thanks!

I'm going to start using this release process for all projects that use zproject.

  • project.xml always specifies next release
  • releases are made in github using the "release" functionality
  • after a github release we update the project.xml version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants