RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2025-04-01 22:48:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

DEV: patchbot: prepare for new version 3.1-dev

Browse Source 
The bot will now load the prompt for the upcoming 3.1 version so we have
to rename the files and update their contents to match the current version.
This commit is contained in:
Willy Tarreau 2024-05-29 14:38:21 +02:00
parent 8452a3f7c9
commit bb7e62b98a
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
dev/patchbot/prompts/prompt15-3.0-mist7bv2-pfx.txt → dev/patchbot/prompts/prompt15-3.1-mist7bv2-pfx.txt
View File

@ -14,11 +14,11 @@ that are picked from the development branch.
Branches are numbered in 0.1 increments. Every 6 months, upon a new major Branches are numbered in 0.1 increments. Every 6 months, upon a new major
release, the development branch enters maintenance and a new development branch release, the development branch enters maintenance and a new development branch
is created with a new, higher version. The current development branch is is created with a new, higher version. The current development branch is
3.0-dev, and maintenance branches are 2.9 and below. 3.1-dev, and maintenance branches are 3.0 and below.
Fixes created in the development branch for issues that were introduced in an Fixes created in the development branch for issues that were introduced in an
earlier branch are applied in descending order to each and every version till earlier branch are applied in descending order to each and every version till
that branch that introduced the issue: 2.9 first, then 2.8, then 2.7 and so that branch that introduced the issue: 3.0 first, then 2.9, then 2.8 and so
on. This operation is called "backporting". A fix for an issue is never on. This operation is called "backporting". A fix for an issue is never
backported beyond the branch that introduced the issue. An important point is backported beyond the branch that introduced the issue. An important point is
that the project maintainers really aim at zero regression in maintenance that the project maintainers really aim at zero regression in maintenance

2
dev/patchbot/prompts/prompt15-3.0-mist7bv2-sfx.txt → dev/patchbot/prompts/prompt15-3.1-mist7bv2-sfx.txt
View File

@ -17,7 +17,7 @@ Finally, based on your analysis, give your general conclusion as "Conclusion: X"
where X is a single word among: where X is a single word among:
- "yes", if you recommend to backport the patch right now either because - "yes", if you recommend to backport the patch right now either because
it explicitly states this or because it's a fix for a bug that affects it explicitly states this or because it's a fix for a bug that affects
a maintenance branch (2.9 or lower); a maintenance branch (3.0 or lower);
- "wait", if this patch explicitly mentions that it must be backported, but - "wait", if this patch explicitly mentions that it must be backported, but
only after waiting some time. only after waiting some time.
- "no", if nothing clearly indicates a necessity to backport this patch (e.g. - "no", if nothing clearly indicates a necessity to backport this patch (e.g.