I guess this marker is that the issue is either "blocker" or "critical" (+ the fix has to be in Jenkins for at least cca 2 weeks).
I'm asking because someone could forget to bump the issue to critical (default is "major") or I can miss something (both happened in the past). On Monday 22 October 2012 07:55:18 nicolas de loof wrote: > Makes me wonder : can we have some way on Jira to tag issues as "*request > backport to LTS*", so that LTS management would not require you to do such > a reminder ? > > 2012/10/21 Vojtech Juranek <[email protected]> > > > Hi, > > as agreed on the last Jenkins meeting [1], next LTS will be based on > > 1.480. > > I identified and backported following bug fixes: > > > > JENKINS-13336 Invalid JSON is produced during remote api operations [2] > > JENKINS-14667 java.io.InvalidClassException [3] > > JENKINS-15277 Check view permissions before showing config page [4] > > JENKINS-15493 Excessive memory usage with large number of request threads > > [5] > > > > Please let me know by Tuesday if there are any other critical or blocker > > issues need to be backported to 1.480.1. As also agree on the meeting, RC > > should be available by Wednesday. > > > > Thanks > > Vojta > > > > [1] > > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html > > [2] https://issues.jenkins-ci.org/browse/JENKINS-13336 > > [3] https://issues.jenkins-ci.org/browse/JENKINS-14667 > > [4] https://issues.jenkins-ci.org/browse/JENKINS-15277 > > [5] https://issues.jenkins-ci.org/browse/JENKINS-15493
