September 18, 2023 Governance Board Agenda

34 views
Skip to first unread message

Mark Waite

unread,
Sep 18, 2023, 12:41:27 PM9/18/23
to Jenkins Developers
The Jenkins governance board meets today at 6:00 PM UTC on Zoom.  The Zoom URL is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Agenda

NewsAction Items
  • Alexander Brandes and Ullrich Hafner run the officer and board elections for 2023
  • Mark Waite retrospective on signing certificate renewal process and its improvements
    • Code signing certificate update for MSI and WAR files
    • PGP signing key update for RPM and DEB files
      • Debian key packaging improvements (some other projects use that technique now)
      • Notification and process improvements
        • Reimbursement improvements
      • Details being gathered in the retrospective document
  • Mark Waite submit jenkins.io pull request to combine subprojects and SIGs into a single concept - “working groups”
    • More pull requests needed
  • Retire the Chinese Jenkins site - deadline for 4 weeks to close (Kevin Martens)
  • Mark Waite draft a proposal to the board for license policy and phrasing changes
    • Allow other licenses like the JSON license
    • Some other approach?
    • What license should be used for a library plugin?
      • License of the wrapped library (if wrapped library has no separate code, then seems likely)
      • MIT license as used by Jenkins plugins (if abstraction layer in the plugin, then MIT for ours?)
  • Mark Waite submit pull request to replace ICRC link with URC link on top page (done and merged)
Governance Topics
  • Board and officer elections - Ulli Hafner
Community activity
  • Java 11, 17, and 21 in Jenkins - Mark Waite
    • Google doc describes plan that has been discussed with Jenkins board and Jenkins officers
      • Further discussion in this meeting?
      • Diagram that illustrates the transition process to “2+2+2”
    • Summary of discussions
      • Jenkins developers mailing list - Mark Waite to send
      • Jenkins users mailing list - Mark Waite to send
      • Jenkins enhancement proposal - Mark Waite to create JEP
    • Key dates upcoming
      • Sep 19, 2023 - Java 21 release
      • Oct 3, 2023 - Java 11 end of life monitor visible in Jenkins weekly
      • Oct xx, 2023 - Java 21 supported by Jenkins core and many plugins
      • Dec 13, 2023 - Java 11 end of life monitor visible in Jenkins LTS
      • Aug 7, 2024 - Last Jenkins LTS release to support Java 11
      • Sep 4, 2024 - First Jenkins LTS to require Java 17
      • Oct 2024 - end of Java 11 support by Jenkins project
  • Artifactory bandwidth reduction project https://repo.jenkins-ci.org
    • JFrog requests implemented and announced in blog post
      • Open issues being addressed by infrastructure team
  • Prototype.js removal
    • Oct 3, 2023 proposed as the date to remove Prototype.js from Jenkins core
    • Prototype.js removal epic making good progress
    • Tracking sheet shows details
    • Most popular plugins already updated, with few exceptions
      • JFrog Artifactory (work starts in September - 23000 installs)
      • Microfocus Fortify (expected in September or October - 4200 installs)
      • Xray test management for Jira (no response - 1900 installs)
      • Synopsys Coverity (no response - 1400 installs)
      • Tricentis qTest (no response - 1300 installs)
    • Feature flag available to disable prototype in Jenkins core 2.406 and later
  • Hacktoberfest preparation has started

Jenkins Developers

unread,
Sep 19, 2023, 10:32:00 AM9/19/23
to Jenkins Developers
>  Java 11, 17, and 21 in Jenkins - Mark Waite
  • Google doc describes plan that has been discussed with Jenkins board and Jenkins officers
    • Further discussion in this meeting?
    • Diagram that illustrates the transition process to “2+2+2”

I have no comment rights on the google doc but to call this 2+2+2 is confusing.

> In order to limit Java support to two LTS releases, the Jenkins project will adopt a “2+2+2” model where a new Java LTS release is supported for two years, then becomes the minimum required Java version for two years, then is unsupported for two years.

This is because it is not "unsupported" for 2 years, but rather it is "will not run at all, ever again" due to the minimum java baseline being beyond this unsupported version, thus there is no point mentioning it is unsupported for 2 years - it may as well be unsupported for 1 hour or 1000 years.


/James

Daniel Beck

unread,
Sep 19, 2023, 10:57:02 AM9/19/23
to jenkin...@googlegroups.com
On Tue, Sep 19, 2023 at 4:32 PM 'Jenkins Developers' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
> In order to limit Java support to two LTS releases, the Jenkins project will adopt a “2+2+2” model where a new Java LTS release is supported for two years, then becomes the minimum required Java version for two years, then is unsupported for two years.

This is because it is not "unsupported" for 2 years, but rather it is "will not run at all, ever again" due to the minimum java baseline being beyond this unsupported version, thus there is no point mentioning it is unsupported for 2 years - it may as well be unsupported for 1 hour or 1000 years.

I think the idea is that during this last 2 year period, Java itself remains vendor-supported, but cannot run Jenkins anymore. Specifically mentioning that seems useful.
Reply all
Reply to author
Forward
0 new messages