Skip to content

TEE Bidding and Auction services (B&A) release schedule and support window proposal #87

@dankocoj-google

Description

@dankocoj-google

B&A is proposing a release schedule and support window of released versions for the time horizon of 2025 and beyond. Please share any feedback. This is a sibling proposal to the TEE KV.

Support Window

Starting from H1 2025 (roughly per the scale testing timelines), a released version of the Bidding and Auction services is supported for no less than 180 days since the date of its release.

The Bidding and Auction repository will mark releases with relevant information to indicate minimum supported versions and version deprecations.

Support Window Considerations

End of support will not happen during the following major holiday seasons:

  1. New Year holiday season (December through mid-January)
  2. End of support will not happen at the end of the month (last 5 business days of the month).

Please file a Github issue if you think there are other times that should be taken into consideration.

Support Coverage

Patches to actively supported versions will be released for the following incidents:

  1. Security vulnerability patches for the system and its dependencies
  2. Critical bug fixes

In cases of severe security vulnerabilities, we may choose to deprecate a supported version earlier than 180 days from its release. However, we will communicate with all affected parties to establish and approve a timeline first. Also, the B&A release page will be updated with the minimum supported version.

Onboarding and troubleshooting (non-emergency consultation and emergency oncall) support is provided for actively supported versions.

Consultation support will be provided to non-active versions only if questions are filed as Github issues and the support will be provided on a best-effort basis. For bugs, fixes will not be patched to the non-active versions and will instead be added to the next released version (and other active versions if the fix meets the patching criteria).

Release Cadence

A new official release is provided with a rough (but non-committal) cadence of once every three weeks. In between releases there can be unbounded patch releases for the covered support mentioned above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions