"testing" branch is always seen as active by Jenkins
… because it has commits on top of stable, currently:
- 36461295 <— anonym, I can’t find in our release process what makes us do that after releasing something based on testing; any hint?
- 453f5da4 <— bertagaz, same question as above
- 8cc9c3dd <— bertagaz, same question as above
The effect is that our Jenkins setup tries to build testing, which is unmaintainted except during freezes, and as a result release managers are constantly and needlessly spammed.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information