* 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>
* Release Drafter: Do not use `regression-fix` label for the changelog, clarify the category headers
* Release Drafter: use categories from the org-wide settings
* Add the maintainer checklist to the pull request template
* Add checklist items for LTS
* Add "Proposed changelog entries" to the pull request template
* Pull request template: `Internal: ` prefix is now added automatically by the Core Changelog generator
https://github.com/jenkinsci/jenkins-core-changelog-generator/pull/6
* Apply suggestions from review by @MarkEWaite
Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com>
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
* Update PULL_REQUEST_TEMPLATE.md
Removed a defunct hyperlink and placed an intuitive directive in its place.
* Updated PULL_REQUEST_TEMPLATE.md to include comment
* Updated PULL_REQUEST_TEMPLATE.md to include lts backporting
* Remove the description header. It is confusing because commit message body goes before it
* Explicitly require human-readable changelogs
* Explicitly require links to the external changelogs/diffs
* Introduce the pull-request template.
This change xplicitly sets expectations from pull requests.
Reason:
* Highlight the need in autotests and JIRA issues for bugfixes
* ask PR creators to propose the changelog entries for their changes.
* Provide hints about referencing people
* Move the pull request template to .github