The plan looks good to me.
I'm also thinking about dropping the .NET 2.0 support in Windows installer
and windows-slave-installer. If we drop Java 7, I would like to join the
party and to announce the .NET2 and 3.5 deprecation and selection of .NET4
as a baseline.
.NET 4 is 5 years old && available on Operating systems including the
latest Windows XP service pack. The situation with Embedded Windows
versions is a bit worse, so we may still impact a particular subset of
If there is no strong -1s, I will start a standalone discussion of it.
P.S: Maybe we also want to discontinue support of Windows 32 bit systems
and other such stuff. But it's very debatable
2016-12-01 9:08 GMT+01:00 ogondza <ogon...@gmail.com>:
> I am undecided on the subject. There clearly always are reasons to use
> newer/better version but is JDK 7 support really blocking us somewhere?
> Bugs we cannot fix / need to awkwardly compensate, features we can not
> deliver on Java 7?
> I felt much stronger against dropping Java 6 as we identified several
> architecture/OS combinations with no Java 7+ vendor making the platforms
> (RHEL4, itanium architecture, Solaris 9 (IIRC)) not usable as Jenkins
> nodes. (Yes, you can run agent on older Java version but it causes subtle
> problems.) However, oracle does not seem to drop any of the platforms (at
> least those we care for) between 7 and 8.
> What we can do right now, to make this a bit less troublesome to users and
> easier to digest for community, is creating a general time plan for
> dropping support of JDKs (or other things) we would follow in specific
> cases. Something like:
> - Month 0: Announce the intention publicly, with this plan attached.
> - Month 3: Drop support for Jenkins weekly. Declare what LTS will be the
> last one to support the think we are dropping. Since we gave people time to
> get prepared, we do not have to try hard to prolong the support in LTS
> branch. IOW, I see no reason to do whole new LTS line after the support was
> dropped for weeklies.
> - Month 3-5: LTS.1 with support dropped is released.
> - Month 12?: In case of Java, encourage the use from plugins / use it as
> default. Extending the support in plugins allow people to consume plugin
> updates/fixes after upstream has dropped support without upgrading Java.
> This is especially subtle as IIRC plugin manager offers plugin updates
> (perhaps even core ones) that require newer Java version than the one
> installed on master, and there is no guarantee plugin that needs Java 8
> require core with same requirement.
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> To unsubscribe from this group and all its topics, send an email to
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
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 view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.