List view
- No due date•0/13 issues closed
- No due date
- No due date•2/33 issues closed
- No due date
- No due date•1/14 issues closed
- Due by May 22, 2026•0/10 issues closed
We can close this milestone when the generator: - Supports retry loops for simple unary operations - Supports pagination - Supports LROs - Can generate working code for google/cloud/workflows/v1
No due date•2/10 issues closed- No due date•10/23 issues closed
- No due date•18/25 issues closed
After GA we will want to add more features, and sometimes we want to be explicit about features that will not be part of GA.
No due date•0/1 issues closedThis list includes any items that must be cleared after public preview and before GA.
Due by September 15, 2026- No due date•9/29 issues closed
- No due date•0/5 issues closed
- Due by May 8, 2026•4/17 issues closed
We can close this milestone when the output of the generator for `secretmanager-v1` and 100 other clients is of sufficient quality to create a "public preview" release. This is a good milestone to record "before GA but after MVP" items, such as: - The generated documentation comments are correct and readable. - The generated code has good examples. - The generated code includes pagination and LRO helpers. - The generated code has configuration parameters for retry and polling loops.
No due date•3/26 issues closedWe can close this milestone when the generator produces working code for `google-cloud-secretmanager-v1`. That is, the generated code must compile and we must be able to write integration tests. There are external (to librarian) dependencies such as the well-know types, a gax library, etc.
No due date•28/29 issues closed- No due date•0/2 issues closed
- No due date•1/2 issues closed
- No due date•0/37 issues closed
- No due date•1/13 issues closed
- No due date
- No due date•1/10 issues closed
- No due date•0/1 issues closed
- No due date•2/7 issues closed
- No due date•0/2 issues closed
- No due date•8/32 issues closed
- No due date•10/16 issues closed
Design and implement a clear source of truth for every aspect of configuration
No due date•1/8 issues closedAny issue that hasn't been prioritized yet for surfer project.
No due date•39/78 issues closed- No due date•34/68 issues closed
These are any tickets that should be looked into to support existing customers.
No due date•140/143 issues closedBucket 3: Items Requiring Broad Alignment & Org-Wide Rollout These are large-scale initiatives affecting all repositories and teams, requiring a clear communication and phased rollout plan.
No due date•7/24 issues closedBucket 2: Items Requiring Design & Project Work These items require dedicated design, discussion, and prototyping before org-wide implementation.
No due date•0/13 issues closedWe plan to deprecate/migrate bots in https://github.com/googleapis/repo-automation-bots as part of the librarian project. This milestone tracks progress towards that work. This milestones contains bots that are ready to start deprecation. Plan to follow the bot deprecation framework: go/cloud-sdk-bot-deprecation-framework
No due date•51/69 issues closedWork that has been triaged but not yet planned. This milestone is used to distinguish it from untriaged issues, which will have no milestone assigned.
No due date•111/134 issues closed