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

Version Numbers and Backward Incompatibility Question #2082

Closed
dankirkd opened this issue May 22, 2017 · 1 comment
Closed

Version Numbers and Backward Incompatibility Question #2082

dankirkd opened this issue May 22, 2017 · 1 comment
Assignees
Labels
type: question Request for information or clarification. Not an issue.

Comments

@dankirkd
Copy link

The version history for this library went from "0.8.0" and never being an "alpha" version to "0.8.1-alpha", and always since being an "alpha" release.

I believe that this explains that: #1471

However, can you confirm that when you talk about backward incompatibility you are just talking about the evolving library, class and package name, and not that a message produced using 0.18.0-alpha cannot be read by a client that uses 0.8.0, for example? That would seem unlikely since I cannot pin Google PubSub topics to a given version, right?

@tcoffee-google tcoffee-google added the type: question Request for information or clarification. Not an issue. label May 22, 2017
@tcoffee-google
Copy link
Contributor

Yes, these version numbers refer only to the client library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants