> • Is this something for the governance board to decide at the next > meeting?
Next meeting's agenda is already more than full. > People have their opinions but we need to move forward to reach a decision of > which there is not one solution that meets everyone's requirements. We should know what the side effects are though (including JDK availability on the systems our users use), and communicate accordingly. Right now, I don't even know how availability of JDK 8 is for various common platforms Jenkins runs on. If increasing the JDK requirement means we need to discontinue some of the native installers, then that's fine with me in principle, if we know in advance and can plan accordingly (e.g. provide extensive 'manual installation' instructions). But increasing the system requirements such that the installers simply become useless would hurt users who rely an them and rightfully expect them to work*. They exist and are essentially the recommended way to install Jenkins (https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins), so we should support them, and fix their shortcomings, rather than ignore them. Jenkins is difficult enough to start using as it is. Let's not make it worse. Why don't we start by setting up a configuration survey, asking the users list, and putting banners up on the wiki, Jira, jenkins-ci.org? Then we'd at least have some data to base any decisions on. -- 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/560A0115-C06F-409C-B10D-ED639698AF04%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
