Cloud Connector 17.0 Planning
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
Capacity
List any noteworthy PTO that may impact the capacity for the planned milestone
Team Member | PTO Dates |
---|---|
@rzwambag | 2024-04-19 ~ 2024-04-22 |
@alipniagov | 2024-05-03 ~ 2024-05-06 |
@rzwambag / @mkaeppler | 2024-05-09 |
Team is a 90% capacity
Key Dates
- Kickoff is on 2024-04-22
- Release is on 2024-05-16
Planning
Indicate major efforts by linking to the appropriate epic. Under each epic indicate who is focusing on these efforts and list the individual issues assigned for this milestone.
Top Priority Items
Ordered from highest-to-lowest priority.
who: Nikola, Aleksei
Enable Chat-as-a-Platform We have been working on alignment with other stakeholder teams. In this milestone we will complete two Epics related to Unit Primitives
- https://gitlab.com/groups/gitlab-org/-/epics/13116+
- https://gitlab.com/groups/gitlab-org/-/epics/13103+
And provide input/support as other teams work on https://gitlab.com/gitlab-org/gitlab/-/issues/446206+
https://gitlab.com/groups/gitlab-org/-/epics/13610+ who: Aleksei, Matthias
- For %17.0, our goal is to clarify whether a "simple solution" will suffice to resolve the noisy neighbour problem.
- At this time, we have a strong belief that it likely will. This mean our technical solution for noisy neighbours will be different from our solution to having fair share usage. Based on this belief, we are explicit de-scope fair share usage from %17.0.
- If we discover the "simple solution" is not sufficient / appropriate, we will explore fair share usage in our next milestone (not in %17.0).
- We discovered a bug in the current limits and are working to get this fixed
Improved Code Suggestions Architecture to Decre... (gitlab-org&12224) who: Roy, Matthias
- Multi region AI gateways are expected by end of April
- In order for gitlab.com to take advantage of this, we need to to support direct IDE->cloud.gitlab.com->AI gateway traffic
- At least for gitlab.com, but ideally in a way that the same path is taken for Self Managed customers as of 17.0
- Given competing priorities and limitations to team capacity, this is our most-likely-to-drop item if something needs to give.
Secondary Priority Items
Continue to support the monetization of Code Suggestions and maturing Chat on self-managed.
- Our current plan continues to support Chat towards maturity and free-access-cutoff. We will be reviewing our go/no-go criteria for cut-off on June 4, 2024. We estimate our level of effort on this to be "supporting AI framework".
Chat Post-GA AI Features
- Establish if there is any Cloud Connector related work required in order to support the next AI features (that are not based on Chat) releasing to Self Managed and Dedicated customers.
<strong data-sourcepos="61:6-61:71">Release Cloud Connector X Observability Integration Experiment</strong>
- Expect Cloud Connector work to be completed by the time this milestone begins
Code Suggestions Post Service Start/Cutoff date... (gitlab-org&12611)
- To complete this Epic/OKR, there is only one small deprecation issue left that we should complete in 17.0
https://gitlab.com/groups/gitlab-org/-/epics/12996+
- Refine in 17.0, and perhaps start on db related tasks
%17.0 as of Apr 23, 2024
Descoped from- Proposal - gitlab.com can sync with CustomersDot (gitlab-org&12714)
- https://gitlab.com/groups/gitlab-org/-/epics/12032+