Skip to content

refresh release process #2109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

refresh release process #2109

wants to merge 8 commits into from

Conversation

@shainaraskas
Copy link
Contributor

@shainaraskas shainaraskas commented Oct 24, 2025 •
edited
Loading

Update the tutorial we have for bumping a version in docs v3

After we have this centralized tutorial, we can cut down on steps in templates so we can reduce the # of surfaces that need to be updated when this process is enhanced (e.g. https://github.com/elastic/dev/pull/3321, https://github.com/elastic/dev/pull/3326, +++++)

Also fixed some stray references to including the base version in the legacy versions array (no longer needed as of #1865)

@shainaraskas shainaraskas requested review from a team as code owners October 24, 2025 19:19
@github-actions
Copy link

github-actions bot commented Oct 24, 2025 •
edited
Loading

🔍 Preview links for changed docs

@shainaraskas shainaraskas added the documentation Improvements or additions to documentation label Oct 24, 2025
reakaleek
reakaleek reviewed Oct 28, 2025
View reviewed changes
reakaleek
reakaleek reviewed Oct 28, 2025
View reviewed changes
reakaleek
reakaleek reviewed Oct 28, 2025
View reviewed changes
shainaraskas
shainaraskas commented Oct 28, 2025
View reviewed changes
@shainaraskas
Copy link
Contributor Author

shainaraskas commented Oct 28, 2025

@reakaleek can you spot check my changes please? :)

@shainaraskas shainaraskas marked this pull request as draft October 30, 2025 15:46
@shainaraskas
Copy link
Contributor Author

shainaraskas commented Nov 13, 2025 •
edited
Loading

Updated the procedure based on our experience with the ECE + ECK releases:

  • only docs-engineering can approve and merge the config changes in staging and prod
  • the version bump PR must be held until release day. if it is merged early, it blocks all other version bumps and bumps of docs-builder features

as a result, I split the process into two phases:

  • prep (config-related PRs in docs-builder)
  • release day (merging the config changes, shepherding the changes into staging and prod)

@Mpdreamz please take a look :)

@shainaraskas shainaraskas marked this pull request as ready for review November 13, 2025 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Mpdreamz Mpdreamz Awaiting requested review from Mpdreamz Mpdreamz is a code owner automatically assigned from elastic/docs-engineering

@colleenmcginnis colleenmcginnis Awaiting requested review from colleenmcginnis

@reakaleek reakaleek Awaiting requested review from reakaleek

Assignees

No one assigned

Labels

documentation Improvements or additions to documentation

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@shainaraskas @reakaleek