[LTS] - Jenkins 2.7.2 timeline and backporting windows

[Oleg Nenashev]

Hi,

Today we had a chat with Oliver regarding 2.7.2 release timeline and bugfix backporting windows. Below you can find a summary, which is a detalized version of the process described on the LTS Release Line page. Oliver is going to update that page soon.

So the Jenkins 2.7.2 timeline is...

• before July 10 => "backporting" time ends (estimate)
  
• If the fix gets integrated into the master branch by this date, it will be available in 2 weekly releases by the RC cutoff
• Integrated bug fixes will be likely automatically backported into 2.7.2
• Exception: barely reviewable or dangerous fixes (we don't want to cause new regressions)
  
• Hint: After merging to master please setup the lts-candidate label to the issue
• July 10 ... July 20 => "backporting of high-priority fixes"
• Fixes during this timeframe do not comply with the 2 weekly release practice
• Each fix backporting should be proposed in the mailing list and reviewed individually
  
• If the fix is reviewable && safe enough, it may be backported
• the decision will be made depending on the bug severity and LTS team capacity
  
• July 20 - Backporting of bugfixes for RC ends
• est. July 21 - RC candidate, testing starts
• July 20 .. August 2 - Release candidate testing
• During this period serious regressions and Blocker issues may be backported
• Each issue requires an individual review together with the release officer (Oliver Gondža)
  
• August 3 - Release

Best regards,
Oleg Nenashev

[Oleg Nenashev]

Amendment for the first bullet:

•   "backporting" time ends (estimate) should be replaced by "common development process"