On 2017-11-20 08:31, Oleg Nenashev wrote:
Hi,
LTS release break looks good to me.
We have lots of pending bugfix-alike changes in pull requests, and
these 2 weeks also give a chance to integrate more into Weekly releases
and then consider these changes for .3 backporting.
Wouldn't it be advantageous to move this RC back to Jan 3 to allow
for more flexibility in backporting late fixes? Or is there an
advantage to having a four week RC testing period?
+1, we just need to stay a bit conservative while backporting the
things. Or we could have RC-1 and RC-2 (in the case we plan to do weeklies)
I have no strong feelings here. Given the number of potential candidates
Oleg mentioned, It would probably be better to extend the backporting
period so there is more time to integrate those changes. That would be:
* Dec 6th 2017: LTS 2.89.1 (as planned).
* Jan 3rd 2018: LTS 2.89.2 RC.
* Jan 17th 2018: LTS 2.89.2
I do not think 4 week testing window add much value if spread over holidays.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/8930a52a-249c-9db1-77e8-5170d1b290e3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
