On 2017-07-27 07:19, Andreas Mandel wrote:
Thanks for the feedback. Does this mean, according to plan, you release
LTS versions even with blocker issues? Or do you judge the severity of
the issue different?
We are trying to narrow this further down to the versions you have
mentioned in the ticket but time is unfortunately quite limited.
The severity of the issue affects the likelihood someone will work on
that in the near future but that is pretty much it. So if we do not have
the fix, the LTS will not be postponed to incorporate it. And even if we
do, I tend to prefer to have the fix soaked in weakly first unless the
bug is particularly bag to outweigh the risks.
Try to look at it this way, the regression has sneaked in, quite likely,
despite the review process and testing when community had all the time
to incorporated it. Trying to device a fix in a hurry and expedite it
into the stable branch has a potential to cause lot more damage.
Especially if we do not have a QE army to verity the result, which we do
not have.
--
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/a9d87944-da8b-e050-0bec-865f45fc4d55%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
