-
Notifications
You must be signed in to change notification settings - Fork 374
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
Announce that -spanner will be moving in N days #3591
Labels
api: spanner
Issues related to the Spanner API.
type: process
A process-related concern. May include testing, release, or the like.
Milestone
Comments
coryan
added
type: process
A process-related concern. May include testing, release, or the like.
and removed
triage me
I really want to be triaged.
labels
Mar 28, 2020
Tasks:
|
devjgm
added a commit
to devjgm/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
devjgm
added a commit
to devjgm/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
devjgm
added a commit
to devjgm/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
devjgm
added a commit
to devjgm/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
devjgm
added a commit
to devjgm/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
devjgm
added a commit
to googleapis/google-cloud-cpp-spanner
that referenced
this issue
Mar 30, 2020
Assigning this to @scotthart since he'll do the next announcement. |
Should we close this? Seems like we took both steps referenced above? |
Yeppers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: spanner
Issues related to the Spanner API.
type: process
A process-related concern. May include testing, release, or the like.
For Spanner, I think N = 60
We want to give customers a heads up that the -spanner repo will be moving into the monorepo at -cpp. We should cut a release and and include an announcement that this will be happening. We may also want to drop a note in our slack channel and anywhere else we can, like on the README.md.
The text was updated successfully, but these errors were encountered: