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

Should we create a branch for the datastore v1beta3 update? #159

Closed
ajkannan opened this issue Sep 10, 2015 · 6 comments
Closed

Should we create a branch for the datastore v1beta3 update? #159

ajkannan opened this issue Sep 10, 2015 · 6 comments
Assignees
Labels
type: question Request for information or clarification. Not an issue.

Comments

@ajkannan
Copy link

The datastore update from v1beta2 to v1beta3 requires touching a lot of code. It would be useful to create a branch off the master branch to provide people with ample opportunity to comment on the changes before it is merged into the master branch. Moreover, a separate branch would allow for smaller PRs, reducing the chance that important changes are buried.

@ajkannan ajkannan added the type: question Request for information or clarification. Not an issue. label Sep 10, 2015
@ajkannan
Copy link
Author

cc/ @aozarov

@jgeewax
Copy link

jgeewax commented Sep 10, 2015

@dhermes @stephenplusplus -- thoughts?

On Thu, Sep 10, 2015 at 1:01 PM, Ajay Kannan [email protected]
wrote:

cc/ @aozarov https://github.com/aozarov


Reply to this email directly or view it on GitHub
#159 (comment)
.

@dhermes
Copy link

dhermes commented Sep 10, 2015

I think it's a fine idea, though I'd add that it's probably a good idea to continually rebase the branch on top of master.

It's not entirely clear this is necessary. Do you advise people to install from HEAD? How often do you cut releases?


Aside:

  1. Is v1beta3 that different?
  2. Should gcloud-python start working on v1beta3 changes?
  3. When is v1beta3 "live"?

@ajkannan
Copy link
Author

We suggest pulling the dependency via release/snapshots pushed to the central repository. Snapshots are updated whenever Travis runs (and the version in the pom.xml file contains the word "snapshot," which is most of the time).

I'll defer on answering the "aside" questions for the time being because I'm not absolutely sure. I know there are a lot of cosmetic changes and a couple behavioral changes (which is why this PR will be large).

@stephenplusplus
Copy link

Moreover, a separate branch would allow for smaller PRs, reducing the chance that important changes are buried.

I personally like the idea of a single commit (or group of commits that occurred in series) to represent such a large change. But, wouldn't this be problematic for your releases if you have partial support for the new API version?

Disclaimer: I intentionally try to avoid git discussions, because there are so many workflows and developers tend to keep close to what they're comfortable with. In the end, all roads take you to the same place, so I encourage whatever is most logical for the team and project. If what I said before doesn't apply or you feel those aren't rational concerns, just do your thing and don't waste any time talking about git :)

@aozarov
Copy link
Contributor

aozarov commented Sep 11, 2015

Is v1beta3 that different?

It is based on proto3 and was changed to use some of its features such as map and oneof, so there
are many structural changes. No real new features but it fixed known/missing issues such as
cursor per query result item and providing the query in the query result which, I think, is necessary for continuation of GQL queries.

Should gcloud-python start working on v1beta3 changes?

You should check with the datastore team when they plan to stop supporting v1beta2 requests.

When is v1beta3 "live"?

Soon, but AFAIK no public date yet.

github-actions bot pushed a commit to suztomo/google-cloud-java that referenced this issue Jun 29, 2022
…is#159)

- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 456641589

Source-Link: googleapis/googleapis@8a251f5

Source-Link: https://github.com/googleapis/googleapis-gen/commit/4ca52a529cf01308d9714950edffbea3560cfbdb
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNGNhNTJhNTI5Y2YwMTMwOGQ5NzE0OTUwZWRmZmJlYTM1NjBjZmJkYiJ9
github-actions bot pushed a commit that referenced this issue Jul 1, 2022
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/5ae2a465-c5f2-47a0-a06e-68a2666fe368/targets

- [ ] To automatically regenerate this PR, check this box.

PiperOrigin-RevId: 345495218
Source-Link: googleapis/googleapis@0a9a8c8
PiperOrigin-RevId: 345067549
Source-Link: googleapis/googleapis@8cfc6c8
PiperOrigin-RevId: 344134135
Source-Link: googleapis/googleapis@b11a87f
github-actions bot pushed a commit that referenced this issue Jul 1, 2022
🤖 I have created a release \*beep\* \*boop\* 
---
## [0.2.0](https://www.github.com/googleapis/java-workflows/compare/v0.1.4...v0.2.0) (2021-02-22)


### Features

* migrate to microgenerator ([#159](https://www.github.com/googleapis/java-workflows/issues/159)) ([e1b02ec](https://www.github.com/googleapis/java-workflows/commit/e1b02ec868a5b3b4f6768d756f21a5622e49c5c7))


### Bug Fixes

* update repo name ([#182](https://www.github.com/googleapis/java-workflows/issues/182)) ([e8de9cf](https://www.github.com/googleapis/java-workflows/commit/e8de9cfc5a4dcd6e8e47a45c76a2539ec35bfd6d))


### Documentation

* generate sample code in the Java microgenerator ([#185](https://www.github.com/googleapis/java-workflows/issues/185)) ([f075046](https://www.github.com/googleapis/java-workflows/commit/f075046a61e7af785e9fe216976616a14baa14bd))


### Dependencies

* update dependency com.google.cloud:google-cloud-shared-dependencies to v0.16.0 ([#151](https://www.github.com/googleapis/java-workflows/issues/151)) ([5b050ee](https://www.github.com/googleapis/java-workflows/commit/5b050ee48d0a03eb6627aa5d8d1da29c00aecbdd))
* update dependency com.google.cloud:google-cloud-shared-dependencies to v0.16.1 ([3927788](https://www.github.com/googleapis/java-workflows/commit/3927788e36805e6ab016e9211991930ee195c35b))
* update dependency com.google.cloud:google-cloud-shared-dependencies to v0.17.0 ([#166](https://www.github.com/googleapis/java-workflows/issues/166)) ([7bbc64a](https://www.github.com/googleapis/java-workflows/commit/7bbc64a627ad67187c2eec79209b09fa43fc0ce1))
* update dependency com.google.cloud:google-cloud-shared-dependencies to v0.18.0 ([#171](https://www.github.com/googleapis/java-workflows/issues/171)) ([2b16cc3](https://www.github.com/googleapis/java-workflows/commit/2b16cc3cb024e7bed09e3bd3a7bc7ae5611b9643))
* update dependency com.google.cloud:google-cloud-shared-dependencies to v0.19.0 ([#193](https://www.github.com/googleapis/java-workflows/issues/193)) ([96fe1c3](https://www.github.com/googleapis/java-workflows/commit/96fe1c3d7afe3acb8444e5c695b92c5e27790971))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
github-actions bot pushed a commit to suztomo/google-cloud-java that referenced this issue Jul 1, 2022
🤖 I have created a release *beep* *boop*
---


## [1.2.0](googleapis/java-storage-transfer@v1.1.0...v1.2.0) (2022-07-01)


### Features

* Enable REST transport for most of Java and Go clients ([googleapis#159](googleapis/java-storage-transfer#159)) ([484473a](googleapis/java-storage-transfer@484473a))


### Bug Fixes

* update gapic-generator-java with mock service generation fixes ([googleapis#162](googleapis/java-storage-transfer#162)) ([5b46c0c](googleapis/java-storage-transfer@5b46c0c))


### Dependencies

* update dependency com.google.cloud:google-cloud-shared-dependencies to v2.13.0 ([googleapis#158](googleapis/java-storage-transfer#158)) ([8e48e49](googleapis/java-storage-transfer@8e48e49))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
github-actions bot pushed a commit that referenced this issue Aug 16, 2022
…-plugin to v3.4.1 (#159)

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [org.apache.maven.plugins:maven-javadoc-plugin](https://maven.apache.org/plugins/) ([source](https://togithub.com/apache/maven-javadoc-plugin)) | `3.4.0` -> `3.4.1` | [![age](https://badges.renovateapi.com/packages/maven/org.apache.maven.plugins:maven-javadoc-plugin/3.4.1/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/maven/org.apache.maven.plugins:maven-javadoc-plugin/3.4.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/maven/org.apache.maven.plugins:maven-javadoc-plugin/3.4.1/compatibility-slim/3.4.0)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/maven/org.apache.maven.plugins:maven-javadoc-plugin/3.4.1/confidence-slim/3.4.0)](https://docs.renovatebot.com/merge-confidence/) |

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. ⚠ **Warning**: custom changes will be lost.

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/java-iam-admin).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4xNjEuMCIsInVwZGF0ZWRJblZlciI6IjMyLjE2MS4wIn0=-->
github-actions bot pushed a commit that referenced this issue Sep 15, 2022
…ator_java versions (#159)

- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 472750037

Source-Link: googleapis/googleapis@88f2ea3

Source-Link: https://github.com/googleapis/googleapis-gen/commit/230a5588306aae18fe8f2a57f14d4039ad72c901
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMjMwYTU1ODgzMDZhYWUxOGZlOGYyYTU3ZjE0ZDQwMzlhZDcyYzkwMSJ9
github-actions bot pushed a commit that referenced this issue Sep 30, 2022
🤖 I have created a release *beep* *boop*
---


## [1.3.3](googleapis/java-vmmigration@v1.3.2...v1.3.3) (2022-09-29)


### Dependencies

* Update dependency cachetools to v5 ([#162](googleapis/java-vmmigration#162)) ([673c232](googleapis/java-vmmigration@673c232))
* Update dependency certifi to v2022.9.24 ([#142](googleapis/java-vmmigration#142)) ([40be099](googleapis/java-vmmigration@40be099))
* Update dependency charset-normalizer to v2.1.1 ([#146](googleapis/java-vmmigration#146)) ([c82b8bd](googleapis/java-vmmigration@c82b8bd))
* Update dependency click to v8.1.3 ([#147](googleapis/java-vmmigration#147)) ([99e10f7](googleapis/java-vmmigration@99e10f7))
* Update dependency gcp-releasetool to v1.8.8 ([#143](googleapis/java-vmmigration#143)) ([778f845](googleapis/java-vmmigration@778f845))
* Update dependency google-api-core to v2.10.1 ([#148](googleapis/java-vmmigration#148)) ([7b74afa](googleapis/java-vmmigration@7b74afa))
* Update dependency google-auth to v2.12.0 ([#149](googleapis/java-vmmigration#149)) ([6585870](googleapis/java-vmmigration@6585870))
* Update dependency google-cloud-core to v2.3.2 ([#144](googleapis/java-vmmigration#144)) ([cb815f8](googleapis/java-vmmigration@cb815f8))
* Update dependency google-cloud-storage to v2.5.0 ([#150](googleapis/java-vmmigration#150)) ([89e854a](googleapis/java-vmmigration@89e854a))
* Update dependency google-crc32c to v1.5.0 ([#151](googleapis/java-vmmigration#151)) ([dc88700](googleapis/java-vmmigration@dc88700))
* Update dependency googleapis-common-protos to v1.56.4 ([#145](googleapis/java-vmmigration#145)) ([5c8312d](googleapis/java-vmmigration@5c8312d))
* Update dependency importlib-metadata to v4.12.0 ([#152](googleapis/java-vmmigration#152)) ([c4ffddc](googleapis/java-vmmigration@c4ffddc))
* Update dependency jeepney to v0.8.0 ([#153](googleapis/java-vmmigration#153)) ([d84c437](googleapis/java-vmmigration@d84c437))
* Update dependency jinja2 to v3.1.2 ([#154](googleapis/java-vmmigration#154)) ([6682d82](googleapis/java-vmmigration@6682d82))
* Update dependency keyring to v23.9.3 ([#155](googleapis/java-vmmigration#155)) ([3d1a2d6](googleapis/java-vmmigration@3d1a2d6))
* Update dependency markupsafe to v2.1.1 ([#156](googleapis/java-vmmigration#156)) ([5666a1e](googleapis/java-vmmigration@5666a1e))
* Update dependency protobuf to v3.20.2 ([#157](googleapis/java-vmmigration#157)) ([e422694](googleapis/java-vmmigration@e422694))
* Update dependency protobuf to v4 ([#163](googleapis/java-vmmigration#163)) ([39884b8](googleapis/java-vmmigration@39884b8))
* Update dependency pyjwt to v2.5.0 ([#158](googleapis/java-vmmigration#158)) ([af206d0](googleapis/java-vmmigration@af206d0))
* Update dependency requests to v2.28.1 ([#159](googleapis/java-vmmigration#159)) ([83eb4d1](googleapis/java-vmmigration@83eb4d1))
* Update dependency typing-extensions to v4.3.0 ([#160](googleapis/java-vmmigration#160)) ([9d2cf45](googleapis/java-vmmigration@9d2cf45))
* Update dependency zipp to v3.8.1 ([#161](googleapis/java-vmmigration#161)) ([1ad1a9c](googleapis/java-vmmigration@1ad1a9c))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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

5 participants