thanks Oliver 2016-12-01 9:08 GMT+01:00 ogondza <[email protected]>:
[...] > - 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. > That plan looks sensible to me. I guess we might want to take that decision to the next gov meeting to make it acknowledged and official to get this plan going, isn't it? > - 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. > IMO, this is definitely something we want to improve (as says Jesse with embedding that in plugins metadata somehow), but IMO can be a disconnected discussion. > -- > 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/CANWgJS6yX%3DyUSMpaPYgCvPoyO3%3DCVBVUiHQNbwqhEbJKNr5NNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
