Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Prepare release 0.33.0 #575

Merged
merged 1 commit into from
Dec 14, 2018
Merged

Conversation

objectiser
Copy link
Contributor

Signed-off-by: Gary Brown gary@brownuk.com

Signed-off-by: Gary Brown <gary@brownuk.com>
Copy link
Collaborator

@jpkrohling jpkrohling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@objectiser objectiser merged commit 85cb0be into jaegertracing:master Dec 14, 2018
@ghost ghost removed the review label Dec 14, 2018
@objectiser objectiser deleted the rel033 branch December 14, 2018 15:00
@objectiser
Copy link
Contributor Author

@pavolloffay Tried following the release instructions but it failed on the maven deploy. Tried restarting multiple times, but didn't work. I don't appear to have access to the staging repos, so would you be able to finish the release?

@pavolloffay
Copy link
Member

pavolloffay commented Dec 20, 2018

The release via travis is broken. It has to be done manually. I will release it locally for you now.

For future please ask release rights in sonatype jira https://issues.sonatype.org/browse/OSSRH-34706?jql=text%20~%20%22jaegertracing%22

@mpetazzoni
Copy link
Contributor

@pavolloffay Thanks! I'm not seeing 0.33.0 yet in Maven Central. Were you able to publish the release?

@pavolloffay
Copy link
Member

I have released it this morning. https://repo.maven.apache.org/maven2/io/jaegertracing/jaeger-core/0.33.0/

Let us know if there are any issues.

@mpetazzoni
Copy link
Contributor

io.jaegertracing:jaeger-client still seems to be 0.32.0: https://search.maven.org/search?q=g:io.jaegertracing%20AND%20a:jaeger-client

@pavolloffay
Copy link
Member

pavolloffay commented Dec 22, 2018

I have created #577 to track it separately.

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

Successfully merging this pull request may close these issues.

4 participants