Skip to content

[Docs][Release] Improved documentation about Patch release process #40551

@raulcd

Description

@raulcd

Describe the enhancement requested

We have been doing more patch releases in the last months and I think this is something that will continue to happen.

At the moment we don't have a clear process on how to tag issues that we want to include on the next patch release and, for example, we've had to create a 15.0.2 patch release because the issue that was identified as blocker in order to create the 15.0.1 release was missed when cherry-picking the issues for the release.

We should document how we should tag issues so everyone is aware and also have a minimal process checklist for the Release Manager to follow.

Component(s)

Documentation, Release

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions