Skip to content

Update release lead schedule #5448

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.

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

Merged

Conversation

MarkEWaite
Copy link
Contributor

Update release lead schedule

Rotate Adrien to end of list

Testing done

None. Rely on reviewers to report if their rotation as a release lead needs to be adjusted.

@krisstern and @darinpope you are the next two release leads. Will this schedule work for each of you?

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

Rotate Adrien to end of list
@MarkEWaite MarkEWaite added the documentation Improvements or additions to documentation label Aug 2, 2025
@MarkEWaite MarkEWaite requested a review from a team as a code owner August 2, 2025 11:21
Copy link
Member

@krisstern krisstern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@darinpope darinpope merged commit 403899b into jenkinsci:master Aug 2, 2025
5 checks passed
@MarkEWaite MarkEWaite deleted the update-release-lead-schedule branch August 2, 2025 13:23
@daniel-beck
Copy link
Member

daniel-beck commented Aug 16, 2025

https://github.com/jenkinsci/bom/commits/5164f11035b55596f89822c001230fc588aa832e/CONTRIBUTING.md
FYI every time someone opens a PR to this repo GitHub will tell them the contribution guidelines have been changed. Most of these don't seem to be relevant content that needs to be re-read, perhaps that table can be moved to a file without that magic behavior?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants