Skip to content
This repository was archived by the owner on Jan 30, 2025. It is now read-only.

Milestones

List view

  • February 12, 2025 Release

    The release is scheduled for February 12, 2025. PRs must be submitted and made mergeable by EOD February 5, 2025 (one week before release). This means they should have tests passing and merge conflicts resolved. The description for the PR must include details of what is included in the PR and how to test it, and preferably new tests supporting the update. Any PRs submitted after the deadline will not be included in the release but go in the next release. This includes PRs with tests failing, no description, no screenshots/video demonstrating the update, sufficient Cypress tests, no link to associated JIRA ticket, etc. If no mergeable PRs are submitted for a release, there will be no release that week (unless there is a need for an out-of-cycle release).

    Overdue by 10 month(s)
    •
    Due by February 12, 2025
    0% complete0 open0 closed

  • February 5, 2025 Release

    The release is scheduled for February 5, 2025. PRs must be submitted and made mergeable by EOD January 29, 2025 (one week before release). This means they should have tests passing and merge conflicts resolved. The description for the PR must include details of what is included in the PR and how to test it, and preferably new tests supporting the update. Any PRs submitted after the deadline will not be included in the release but go in the next release. This includes PRs with tests failing, no description, no screenshots/video demonstrating the update, sufficient Cypress tests, no link to associated JIRA ticket, etc. If no mergeable PRs are submitted for a release, there will be no release that week (unless there is a need for an out-of-cycle release).

    Overdue by 11 month(s)
    •
    Due by February 5, 2025
    0% complete0 open0 closed

  • January 29, 2025 Release

    The release is scheduled for January 29, 2025. PRs must be submitted and made mergeable by EOD January 22, 2025 (one week before release). This means they should have tests passing and merge conflicts resolved. The description for the PR must include details of what is included in the PR and how to test it, and preferably new tests supporting the update. Any PRs submitted after the deadline will not be included in the release but go in the next release. This includes PRs with tests failing, no description, no screenshots/video demonstrating the update, sufficient Cypress tests, no link to associated JIRA ticket, etc. If no mergeable PRs are submitted for a release, there will be no release that week (unless there is a need for an out-of-cycle release).

    Overdue by 11 month(s)
    •
    Due by January 29, 2025
    •18/18 issues closed
    100% complete0 open18 closed