those in trunk I backported because were related to SECURITY-49 and need
immediate fix or I consider the fixes as low risk (while problems they fix are
IMHO quite serious).
The only one I don't understand is
JENKINS-16341 and 08efdf5d3ab9
- does replacement of Set by Array reduce memory footprint in any substantial
yes, I'd also expect these to be cherry-picked just before the release
> Can we assume that qualified trunk fixes may be optimistically cherry-picked
> to the ‘stable’ branch and that ‘mvn deploy’ may be used to produce binary
> snapshot WARs for people to play with?
the artifacts like WAR should be available on  (if it fails, I can provide
it on our public Jenkins instance). Once backports are done, I'd expect RC
will be published and there will be some time for testing.
> By the way, in the context of 1.480.1 I mentioned that it would be helpful
> to have a label for LTS backport candidates.
+1, not sure if JIRA didn't provide tags by time when we setup processes for
LTS or there were some other objections, but obviously I'm not able to track
all JIRAs and asking on dev-list is not very effective.