You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0.8.0 designates an alpha version 0.8.0-beta designates a beta, and presumably 1.0.0 will be our first GA
That's well and good for now though a bit confusing. I'd like to suggest that code that from now on, code that is not beta, be designated -alpha and not 0.8.0.
The real problem is when we go GA however. We will have a -SNAPSHOT which is top of tree Master; we will likely have a Pre-Release (or early release), a Current, and a last release.
Unfortunately, maven doesn't really understand -alpha or -beta designations in a clear way. It considers them to be a "qualifier" and sorts them alphabetically. So while it might allow updating from -alpha to -beta, it is unlikely to update to a GA version.
For those of us who use automation (like the versions plugin) this is a bit of a problem.
The auth library chose to go with all release update the major version (first # before the dot).
I wish I had a clear suggestion to go with your desire to be clear that this is a beta release. I don't. But I wish you had gone with a the java standard rather that following the path of some of our other teams and making something up that isn't idiomatic.
Everything GA and after will follow the path you are describing. We are not going to put "-beta" on 1.x+ releases. For pre-1.x, the plan is to currently not have any package where both 0.x.y and 0.x.y-beta exist.
Activity
garrettjonesgoogle commentedon Dec 12, 2016
Everything GA and after will follow the path you are describing. We are not going to put "-beta" on 1.x+ releases. For pre-1.x, the plan is to currently not have any package where both 0.x.y and 0.x.y-beta exist.
garrettjonesgoogle commentedon Jan 11, 2017
Plan of record:
Already-existing packages:
New packages:
garrettjonesgoogle commentedon Jan 11, 2017
Closing out this issue because we have put this plan into action already.
deps: update dependency com.google.cloud:google-cloud-bigquery to v2.…
chore(main): release 2.3.10 (#1472)
deps: update dependency org.junit.vintage:junit-vintage-engine to v5.…
chore(config): migrate config renovate.json (#1471)
deps: update dependency com.google.cloud:sdk-platform-java-config to …
chore(deps): update dependency com.google.cloud:google-cloud-shared-c…
deps: update dependency org.junit.vintage:junit-vintage-engine to v5.…
chore(deps): update dependency com.google.cloud:google-cloud-shared-c…
chore(config): migrate config renovate.json (#1471)
chore: only reset dialect result when it has changed (googleapis#1471)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.…
chore(deps): update dependency com.google.cloud:libraries-bom to v26.…
deps: update dependency org.xerial.snappy:snappy-java to v1.1.9.0 - a…
deps: update dependency org.xerial.snappy:snappy-java to v1.1.9.0 - a…
test(deps): update dependency org.mockito:mockito-core to v4.8.1 (goo…