AI Engineering: Follow the Sun coverage for DAP GA
We want to completely finish the work in flight with confidence for making the Duo Agent Platform GA launch a success. Because of that, I am creating this issue to outline engineering support throughout all time zones until the release cut-off date.
| Feature | Work | Task | Support Needed |
Subject to Dec 15 cutoff? Y/N |
|---|---|---|---|---|
| e.g. "Usage Billing Testing" | Link to Issue or MR | e.g. "This work needs to be successfully tested on staging, MR Review feedback addressed, and merged" |
AMER - APAC - |
Y |
| AI testing of Usage Billing as it relates to Self Managed, Saas, and Dedicated | Ensure that any failures are identified proactively with: overage cut off, instrumentation of billing events, and ultimate output being acceptable for revenue recognition |
AMER - APAC - |
Y | |
| Usage Billing user experience of usage cutoff |
|
AMER - APAC - |
Y Exception is Editor Extensions? |
|
| Clarify who is billed usage by context |
Confirmed with Manav Dec 10th we are good to:
|
AMER - APAC - |
N .com only so can be after code cut off. Could also be after GA date. |
|
| Non-billed grace period for customers on older GitLab versions when usage billing is released | Have proposed implementation to execs. Need their input since it slightly changes impacted customer cohort. Once approved, we an implement |
AMER - APAC - |
N CDot logic so can be after code cut off |
|
| Access cut-off logic should allow code suggestions during grace period for Duo Core users & for Pro/Ent users |
https://gitlab.com/gitlab-org/gitlab/-/issues/583457 for IDE: https://gitlab.com/gitlab-org/gitlab/-/issues/580883 |
AMER - APAC - |
||
| Agentic Chat broken on public Ultimate projects for non-members |
Relates to clarify who is billed by context. Fix to scenario 4. |
AMER - APAC - |
N? Relates to the billing context in edge cases |
|
| @assign functionality for foundational flows: Dev Flow trigger with issue assignment | Work needs to be finished up and merged. | Follow the sun coverage is already established | Y | |
| Editor Extensions DAP visibility conditions for GA | AMER/APAC | |||
| AI catalog feature rollout |
MR link |
@samdbeckham can you add the MR link - added issues |
AMER EMEA APAC |
|
| Warn users about the use of agents locally (in extensions) |
|
|||
|
Users cannot opt out of Agentic Chat in 18.7 without disabling all Duo features |
Global DAP on/off setting |
AMER EMEA APAC |
||
| IDE: Support mid or end chat end-user usage cutoff experience |
https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/issues/1829 https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/issues/1828 |
in Dev by @ohoral |
||
| IDE: Support end-user usage cutoff experience for Code Suggestions in IDEs |
@mosumah is the DRI who is taking this topic, still in dev the icon in the status bar it would be a new feature state change, the MR will be out today by the DRI for review |
|||
|
Filtering out usage events |
https://gitlab.com/gitlab-org/architecture/usage-billing/design-doc/-/issues/45#note_2945693120 |
|||
| Duo Chat: end-user usage cutoff experience for DAP in Chat UI |
MR needs to be closed |
|||
| make Duo Chat generally available (GA) |
MR needs to be merged |
|||
| Make Duo Chat External Trigger features comply with DAP monetization strategy |
MR needs to be closed |
|||
| AIGW - Usage billing instrumentation work |
https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/issues/1741 , https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/issues/1735, https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/issues/1728 |
Feature complete, MRs need to be closed on all of them | ||
| Code Suggestions billing events are missing namespace/root namespace ids |
still in clarification namespace billing |
|||
| Duo Code review GA for core/pro users |
MR needs to be closed |