# Documentation office hours - April 12, 2024

**URL:** <https://community.jenkins.io/t/documentation-office-hours-april-12-2024/14169>\
**Category:** Community\
**Tags:** meeting, sig-docs\
**Created:** [April 12, 2024, 3:14am UTC](https://community.jenkins.io/t/documentation-office-hours-april-12-2024/14169 "2024-04-12T03:14:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [April 12, 2024, 3:14am UTC](https://community.jenkins.io/t/documentation-office-hours-april-12-2024/14169/1 "2024-04-12T03:14:04Z")

</div>

2024-04-12T02:30:00Z

[![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/d/dce9c0c89708df30088177cadc0df692fd7f80d6.jpeg "2024 04 12 Docs Office Hours") ](https://www.youtube.com/watch?v=3KkgjvidlrY)

## 2024-04-12 (Asia)

Attendees

- Mark Waite
- Meg McRoberts
- Kris Stern

Agenda

- LTS 2.440.3 to be released on Apr 17, 2024
  - Kris Stern is the release lead - resolved issues in the release candidate, no negative feedback
    - Working well for Mark Waite

  - Will release the LTS next Wednesday as usual
    - Container image upload for the last several weeks has been disrupted by an HTTP 529
      - Damien has worked with Docker Inc, ultimately split to use multiple IP addresses for upload
      - Check the weekly build Tuesday to see if uploads without issue
      - Run the container build again, containers upload as expected

  - [Pull request for changelog & upgrade guide](https://github.com/jenkins-infra/jenkins.io/pull/7218) has merged
    - [Update to correct author & pr title for Spring entry](https://github.com/jenkins-infra/jenkins.io/pull/7242) (merged, thanks Kris & Mark)

  - [Release candidate build](https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.440.3-rc34568.387f5a_600b_ee/jenkins-war-2.440.3-rc34568.387f5a_600b_ee.war) available for testing - working great for Mark Waite
  - [GitHub release note](https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.440.3-rc) has the correct link

- Weekly 2.453 built and delivered successfully
  - Changelog was updated

- Next LTS baseline is 2.452 ([Discussion in developer mailing list](https://groups.google.com/g/jenkinsci-dev/c/O1eiOF6vz54/m/At30OOuxAAAJ))
  - 2.452.1 needs a release lead, release checklist
  - Planned, but not yet completed

- New [blog post from Kris Stern regarding GSoC application period conclusion](https://github.com/jenkins-infra/jenkins.io/pull/7230)
  - April 19 is the completion of grading, proposals are sent Google
  - Google announces their selections May 1, 2024
  - Blog post is out for the closing of applications
  - Now in the grading period, preparing our submission to Google
    - 75+ submissions to grade, great to see so much activity

  - Alyssa returns from time off just in time to submit to Google

- Versioned docs project
  - Progress continues thanks to Vandit Singh and Kris Stern
  - Working on the Gatsby site, waiting for news from the infra team on the final site
  - Gatsby site is in progress, slowed because the versioned docs site is not yet hosted
    - Infra team needs to provide the hosting location
    - Proposed URL was [docs.jenkins.io](http://docs.jenkins.io) for the versioned documentation
    - Security advisories still need attention on the Gatsby site

- Contributor spotlight
  - [Hervé Le Meur spotlight published](https://contributors.jenkins.io/pages/contributors/herve-le-meur/)
  - Mark Waite will be next after Hervé

- Technical review/validation for pull requests
  - Reaching out to community for volunteers to assist with technical validation of pull requests
  - Let’s add those people to the copy editors group so they can review and he can @mention them.
    - Kris Stern, Mark Waite, Meg McRoberts, Bruno Verachten, and Kevin Martens
    - Have already tried tagging asking for review, worked very well and thanks to Kris for continued review and support.
    - Plugin development topics go to specific people after Kevin has reviewed

- Documenting Pipeline libraries with markdown or plain text or HTML
  - Markus Winter proposed to support markdown for Pipeline library documentation ([PR-117](https://github.com/jenkinsci/pipeline-groovy-lib-plugin/pull/117))
  - Mark Waite has [converted](https://github.com/MarkEWaite/pipeline-library/commit/42ae6f93f294da9eabf361dc5167afe9d1a6348a) his [branch of pipeline-library](https://github.com/MarkEWaite/pipeline-library/tree/my-own-master) to use markdown, works well
  - Requires [markdown formatter plugin](https://plugins.jenkins.io/markdown-formatter/) installed on the Jenkins controller
  - If we update the [ci.jenkins.io Pipeline library](http://ci.jenkins.io), then markdown formatter plugin needs to be installed on [ci.jenkins.io](http://ci.jenkins.io)
  - Mark [created a helpdesk ticket for this](https://github.com/jenkins-infra/helpdesk/issues/4030)
  - Need security to review and provide insight/feedback

- [cdCon 2024](https://cd.foundation/cdcon-2024/) is next week in Seattle
  - CDF and Jenkins awards will be announced