> Nicolas, your logic is not correct in that we only force users to upgrade >> once. >> >> Just because we would require JDK7 does not mean the user needs to >> install JDK7 and then JDK8 when we require JDK8. They can (*if their >> platform supports it*) install JDK8 straight away and run Jenkins >> compiled for JDK7 on it, so they have only one upgrade. >> > > Those users are the one who follow jenkins ML and announcements. I'm > considering here the one who will discover JDK requirement changed, then > will complain and eventually upgrade JDK. Then few month later this would > happen again > > So how do those class of users find out that the JDK requirement has changed and what the new requirement is? If we have documented this in the change log and publicized this on the wiki and they don't ask on the normal support channels then to be brutally honest then I don't care.
If they use the package management to upgrade and don't check the change log - again I don't care. Others do care about the native package - so for those that do care, one of them could step up and put in a pre-install script that spits out the new JDK requirement with suggestions about what to install (and that it will change again in 3 months). Users that are not caught by any of the 2 above - we have no chance of helping anyway - so at which point I will say again I just don't care. -- 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/a99f3f96-a9d3-4ddf-8c76-86d0b11d5861%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
