List view
- No due date•4/4 issues closed
- No due date•15/15 issues closed
All issues blocking the Compute Library from being promoted from experimental to GA.
Due by September 30, 2023•12/12 issues closedFor this milestone we need to add any services that are GA by 2023-05-15, including the services that use REST-only. With some caveats: - This excludes any services that require artisanal hand-crafted layers - This excludes any services that do not publish their protos
Due by June 30, 2023•10/10 issues closedImplement all the `gcs::Client` functions over GCS+gRPC Enable integration tests against production Less than one error per billion uploads and less than one error per billion downloads
Due by September 30, 2022•18/18 issues closedComplete ReadObject() and DeleteObject()
Due by June 30, 2022•2/2 issues closedAt the end of this milestone all GCP (Google Cloud Platform) services that meet these conditions will have a GA library: - The service must be gRPC based - The service must be GA before 2022-11-15 (*and* have its protos published *and* have a working endpoint) - Only the GA version of the service is included (no `v1beta3`) - Services that require an artisanal hand-crafted library are excluded (BigQuery, Pub/Sub Lite) For automatically generated libraries, we need the library to be complete, i.e., cover all the features of the service, have a README, and a quickstart program. No examples, unit tests, or integration tests are required.
Due by December 31, 2022•109/109 issues closedThis is an intermediate milestone for [GCS+gRPC: Public Preview](https://github.com/googleapis/google-cloud-cpp/milestone/39). The goal is to complete as much as possible during 2022/Q1.
Due by March 31, 2022•24/24 issues closedFor many reasons, we want Bigtable to work more like the other libraries. A summary of the mission can be found [here](https://docs.google.com/document/d/1lqVZK4V7Ia1sjKvmSCzYfYsCENllfwHtbwRQZWQlilA/edit#bookmark=id.36hc4ibike2) (internal Google document). Implementation details for Modernizing the Data API can be found [here](https://docs.google.com/document/d/1NjGK7_1gfkxavxFxIHcKoDyxPWGITnYL5JBH18ZNG6A/) (internal Google document). I am closing this milestone because the remaining work is all waiting until we can remove / retire functions. The bugs are enough.
No due date•30/34 issues closedThis milestone follows after [GCS+gRPC: Public Preview M1](https://github.com/googleapis/google-cloud-cpp/milestone/41) At the end of this milestone the C++ plugin with be of sufficient quality for a public preview. Usually this means "ready for GA, except for waiting for any bug reports or feedback to come back." In this case this will include "the top 24 metadata operations" (sometimes "top 19", the actual count is not that relevant until the last few weeks of the deadline). **NOTE:** this is subject to the service public preview release. We may complete the C++ client library plugin and then the service may be delayed for separate reasons.
Due by June 30, 2022•38/38 issues closedAt the end of this milestone we would have implemented the features described in: * https://google.aip.dev/auth/4110 * https://google.aip.dev/auth/4111 * https://google.aip.dev/auth/4112 * https://google.aip.dev/auth/4113 * https://google.aip.dev/auth/4114 * https://google.aip.dev/auth/4115 Note that https://google.aip.dev/auth/4116 is **out of scope** as it is in draft mode.
No due date•9/9 issues closedAt the end of this milestone the existing libraries (bigtable, bigquery, iam, logging, pubsub, spanner, storage) will be able to use unified credentials, and continue to support the current credentials story.
No due date•12/12 issues closedAt the end of this milestone we will have enough implemented to decide if the design in go/cloud-cxx:guac-dd is viable.
Due by June 30, 2021•12/12 issues closed- No due date•2/2 issues closed
This should have a stable API, and lots of integration tests. It may be missing some samples.
No due date•5/5 issues closedWe get to a mostly auto-generated BigQuery Storage Read API client that has support for resuming streaming reads, code checked in to `google/cloud/bigquery`, and an integration test demonstrating basic functionality.
Due by March 26, 2021•6/6 issues closedSmaller tasks (as opposed to projects) that we want to complete in 2021-Q1.
Due by March 31, 2021•7/7 issues closed- Due by December 31, 2020•6/6 issues closed
Complete all the tasks to deem the library ready for preview by our customers.
No due date•26/26 issues closedThe C++ Microgenerator is in active use, I do not think we need to track its work like this.
No due date•31/31 issues closedComplete all the APIs, including admin APIs for Cloud Pub/Sub. Write all the examples for those APIs.
No due date•39/39 issues closedThis is the GA milestone for Cloud Pub/Sub. At this point the surface should be stable, all the functionality is exposed, we have at least one benchmark (and the numbers are not embarrassing), we have implemented all the examples, etc.
Due by December 31, 2020•70/70 issues closedWe want a MVP where applications can publish and subscribe to messages, with more or less the APIs that we will be offering in the final version (but maybe very naive implementations). We also want a location to track bugs that might be moved to a more precisely defined milestone later (e.g. we will have a "GA" milestone at some point).
No due date•15/15 issues closedThis is misc. work that we plan to complete this quarter.
Due by September 30, 2020•5/5 issues closedThis Milestone captures misc. work that we plan to complete in Q2. This is intended to be an easy way for anyone to grab a task that needs to be done "soonish". I plan to create a milestone like this for every quarter.
Due by June 30, 2020•2/2 issues closedComplete the implementation of the GCS+gRPC plugin
No due date•51/51 issues closedTasks to complete after we have a working mono repo, which may be too hard or too low value for effort before then.
Due by June 26, 2020•19/19 issues closedThis milestone covers the work to move the -common repo into this repo at google/cloud/common
Due by June 4, 2020•13/13 issues closedThis milestone covers the work to move the -spanner repo into this repo at google/cloud/spanner
Due by June 1, 2020•22/22 issues closedThis milestone covers the work to move the -bigquery repo into this repo at google/cloud/bigquery
Due by May 21, 2020•9/9 issues closedThis milestone covers the work to move the -pubsub repo into this repo at google/cloud/pubsub. Since this is a non-GA project that we own completely, I think it'll be the easiest to move, and should likely be our first one.
Due by May 21, 2020•18/18 issues closed- Due by May 14, 2020•21/21 issues closed
We need to make this repo ready to function as a monorepo using a single per-repo version number.
Due by April 30, 2020•17/17 issues closedThe goal is to get the PR builds to < 20m, including the -pubsub and -spanner libraries. In general we need to reduce the build times by: * Avoid building things that have not changed, use caching to let the build system take care of it. * Avoid running tests that have not changed * Parallelize unit tests, integration tests, examples and benchmarks, particularly any "slow" ones to reduce latency * Prefer "fast build" modes for PRs, leaving slow builds (e.g. -O2 builds) for post-PR
Due by April 30, 2020•63/63 issues closedList cool features that we want in the Cloud Bigtable C++ client, but are not required for GA or any other specific release milestone.
No due dateI have moved all the tasks out of this milestone and into the "Bigtable GA" milestone: https://github.com/googleapis/google-cloud-cpp/milestone/2
No due dateThe remaining features and fixes to declare GA for the Google Cloud Storage library.
No due date•39/39 issues closedBreakdown the work to implement error handling for the Storage API without exceptions.
Due by February 15, 2019•69/69 issues closedAt the end of this milestone the Cloud Bigtable client will offer asynchronous APIs for all operations.
No due date•90/90 issues closedAll the stuff that we are leaving out of the Beta Release. Closing, this is obsolete and better tracked in https://github.com/googleapis/google-cloud-cpp/projects/16
No due date•14/14 issues closedComplete all the requirements to achieve `Beta` status.
Due by February 15, 2019•130/130 issues closedAt the end of this milestone the library will implement: reading objects of arbitrary size, uploading small objects (< 1GiB), listing the contents of a bucket. The library will implement sensible retry and backoff strategies. The library will be able to log operations for troubleshooting.
Due by June 30, 2018•15/15 issues closedAt the end of this milestone we will be able to access one API through the library (Bucket: get) is a good candidate. The API will have unit tests, will have an integration test executed on each commit and PR, will have Doxygen-level documentation, and a simple code snippet. The API will authenticate with Google Cloud Platform using Google Application Default Credentials. The implementation may miss a number of features, including: more advanced authentication, interesting retry and backoff algorithms, pre-conditions, etc.
Due by June 15, 2018•4/4 issues closedThe list of bugs before we declare that the library is "beta". This assumes that the Alpha Release is completed.
No due date•74/74 issues closedInitial Bigtable client for early adopters. - We should have a complete (synchronous) API for data and admin operations. - We should not expect major changes to the APIs.
Due by March 31, 2018•48/48 issues closedThe checklist for GA is too long to include here, but in general: - The API should be considered stable. - All public methods have at least one usage example. - All supporting examples required for GA are complete. - All public methods and types have comment (aka Doxygen) documentation. - Code coverage above 80% (we are aiming for 90%). - The README is up to date and complete. - The README points to the getting started examples.
Due by June 30, 2019•138/138 issues closedThis is the minimum set of features for a synchronous client.
No due date•35/35 issues closed