Discrepancies between language package versions

[tmccnnll]

The version numbers used for the compiled packages are not consistent across languages.

For example, the current C# package version is 2.2.0, the current Java package version is 2.0.1, and the current PyPI package version is 1.52.0.

When working in a multi-language environment, these discrepancies make it difficult to ensure compatibility between projects. Additionally, if you are using a local clone of this repo to compile your own proto files to be used in your application(s), then aligning the version of the language packages with the version of the protos found in the local clone is very difficult.

Would it be possible to align these version numbers in some way? Ideally, it would be great if the version number was tied to a release tag on this repo.

Related issue: #17

[parthea]

Closing as obsolete. It is recommended to use the googleapis repo instead.

[tmccnnll]

@parthea, what is the relationship between this repo and googleapis?

If the recommendation is to use the latter over this one, can that be documented somewhere in this repo?

[parthea]

Hi @tmccnnll , The protos in this repo also exist in googleapis/googleapis here. The difference is that protos in this repo are outdated and manually synced, where as the googleapis/googleapis are automatically kept up to date. I've created #107 to track updating the README for this repo.

The issue that you opened is for the language specific repos, for example googleapis/python-api-common-protos. The language specific repositories should be updated to also use googleapis/googleapis. This will minimize compatibility issues moving forward.

For python-api-common-protos, I've created googleapis/python-api-common-protos#83 to track this effort.

I'll keep this issue open until all the language specific repos have migrated to use googleapis/googleapis.