Advise GSoC student to follow master for regression testing.
Martin Jambor advises a GSoC student to generally follow master for regression testing unless an issue is specific to a release branch.
Sebastian Galindo asked about which branch to target for regression testing a fix in the OG15 branch (devel/omp/gcc-15). Martin Jambor recommends generally following master unless the issue only manifests on the release branch, in which case testing on that branch is necessary.
- reviewer
Recommends following the master branch for regression testing unless the issue is specific to a release branch.
“I would always recommend following master fairly closely unless you have a specific reason not to”
- other
Acknowledges the advice to compare regression test results with and without the patch on the branch if necessary.
“Sounds good! Thanks for your response.”
In Details
This concerns the process of testing GCC patches, specifically OpenMP/ACC related fixes from GSoC students. Regression testing ensures that changes don't introduce new bugs or break existing functionality. Release branches (OG15) maintain older GCC versions.
For Context
When fixing bugs in software like GCC, it's important to test the fix to ensure it doesn't create new problems. This is called regression testing. GCC has a main development version (master) and stable release versions. This discussion clarifies which version to use when regression testing a specific bug fix.