mirror of
https://github.com/jenkinsci/jenkins.git
synced 2026-11-11 02:56:21 +00:00
478d11e84d
* Draft the new maintainer guide * Maintainer guide - Apply suggestions from code review Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com> Co-Authored-By: Tim Jacomb <t.jacomb@kainos.com> Co-Authored-By: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> * Apply suggestions from code review Co-Authored-By: Jeff Thompson <37345299+jeffret-b@users.noreply.github.com> Co-Authored-By: Francisco Fernández <31063239+fcojfernandez@users.noreply.github.com> * Maintainer guide - Replace the first role by "contributor" * Maintainer guide - Add more details * Maintainer guide - address some feedback * Apply suggestions from code review by @daniel-beck Co-Authored-By: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> * Update .github/PULL_REQUEST_TEMPLATE.md Co-Authored-By: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> * Maintainer guide - more updates * Maintainer Guide: Add info about the Security Releases and merges + add an explicit Jenkins LTS section Addresses comments from @daniel-beck and @olivergondza * Maintainer guide: reference the advisories * Apply suggestions from code review Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com> Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com> Co-Authored-By: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> * Apply suggestions from code review Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com> * Fix typos * Expand code review goals: documentation and code styles * Maintainer guide: Document the squash-merge policy * Apply suggestions from code review Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com> Co-authored-by: Raihaan Shouhell <raihaanhimself@gmail.com> Co-authored-by: Tim Jacomb <t.jacomb@kainos.com> Co-authored-by: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> Co-authored-by: Jeff Thompson <37345299+jeffret-b@users.noreply.github.com> Co-authored-by: Francisco Fernández <31063239+fcojfernandez@users.noreply.github.com> Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
2.8 KiB
2.8 KiB
See JENKINS-XXXXX.
Proposed changelog entries
- Entry 1: Issue, Human-readable Text
- ...
Proposed upgrade guidelines
N/A
Submitter checklist
- (If applicable) Jira issue is well described
- Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
- Fill-in the
Proposed changelog entriessection only if there are breaking changes or other changes which may require extra steps from users during the upgrade
- Fill-in the
- Appropriate autotests or explanation to why this change has no tests
- For dependency updates: links to external changelogs and, if possible, full diffs
Desired reviewers
@mention
Maintainer checklist
Before the changes are marked as ready-for-merge:
- There are at least 2 approvals for the pull request and no outstanding requests for change
- Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
- Changelog entries in the PR title and/or
Proposed changelog entriesare correct - Proper changelog labels are set so that the changelog can be generated automatically
- If the change needs additional upgrade steps from users,
upgrade-guide-neededlabel is set and there is aProposed upgrade guidelinessection in the PR title. (example) - If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as
lts-candidateto be considered (see query).