Labels

May-Jul of 2024. Also, a friendly reminder that GitLab team members should be communicating with Calendar Year publicly as the Fiscal Year does not translate well outside of the company

Aug-Oct of 2024. Also, a friendly reminder that GitLab team members should be communicating with Calendar Year publicly as the Fiscal Year does not translate well outside of the company

Nov of 2024 through Jan of 2025. Also, a friendly reminder that GitLab team members should be communicating with Calendar Year publicly as the Fiscal Year does not translate well outside of the company

Feb-Apr of 2025. When used with Interlock Priority label, do not change once approved.

May-July of 2025. When used with Interlock Priority label, do not change once approved.

Aug-Oct of 2025. When used with Interlock Priority label, do not change once approved.

Oct 2025 to Jan 2026. When used with Interlock Priority label, do not change once approved.

Feb-Apr of 2026

May-Jul of 2026

Aug-Oct of 2026

Oct 2026 to Jan 2027

For AI Assisted/Code Suggestions features - tracking the current version of the feature if it's in Experiment, Beta or GA

For AI Assisted/Code Suggestions features - tracking the current version of the feature if it's in Experiment, Beta or GA

For AI Assisted/Code Suggestions features - tracking the current version of the feature if it's in Experiment, Beta or GA

Required for Readiness Assessment (our first compliance assessment). **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**

Needs to be complete for Security Assessment. See timeline in https://internal-handbook.gitlab.io/handbook/engineering/fedramp-compliance/#key-milestones. **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**

Next step: clarification or information from Compliance