Skip to content

Commit

Permalink
Merge pull request #1108 from junpataleta/backporting
Browse files Browse the repository at this point in the history
Clarify the requirements for backporting
  • Loading branch information
sarjona authored Aug 28, 2024
2 parents dc4d5f2 + f5d5ebb commit 5ef416a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion general/development/policies/backporting.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Should you feel that a new feature or improvement needs backporting, please foll
The integration team will process backport requests, with the following guidelines:

1. The integration team will together consider each request individually considering the needs of the community (influenced by forum posts, moodle partners, discussion with developers via tracker or private message, etc).
2. Backports will happen not earlier than 3 weeks and not later than 2 months after the request was performed.
2. Backport requests will be processed not earlier than 3 weeks and not later than 2 months after the original improvement/new feature has been integrated.
3. Rationale will be given for rejection

If the backport request is approved, please follow the usual development process to submit the feature or improvement on earlier branches. Just to be clear, this means using the new bug number. So, even if the fix you are back-porting cherry-picks cleanly, you will need to amend the commit comment to use the new MDL-XXXXX number.
Expand Down

0 comments on commit 5ef416a

Please sign in to comment.