Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC-10431] Further LTS improvements #18661

Merged
merged 8 commits into from
Aug 2, 2024
Merged

[DOC-10431] Further LTS improvements #18661

merged 8 commits into from
Aug 2, 2024

Conversation

mdlinville
Copy link
Contributor

@mdlinville mdlinville commented Jun 17, 2024

[DOC-10431] Further LTS improvements

  1. Update the logic on the Releases index to get the LTS status from site.data.versions instead of site.data.releases
  2. Update the version switcher to show LTS status both for the currently-viewed page version above the drop-down and in the list of versions in the drop-down
  3. Modify the LTS Maintenance admonition from a red warning to a purple note.
  4. Fix some LTS logic issues including off-by-one errors on LTS maintenance and assistance dates
  5. In the Docker tab, hide the Notes column for all versions except for v23.1 and v22.2.
  6. Fix a display bug each in the Source and Docker tabs

Also added some debug messages and the ability to enable or disable debug in the Releases index and the version switcher. The debug info shows in the page source as HTML comments.

Previews

Description URL Description
Versioned page, not LTS, dev version https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/v24.2/diagnostics-reporting (for example) If the page exists for an LTS version, the entry for that version shows as LTS.
Versioned page, not LTS, stable version, in Assistance Support https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/v24.1/diagnostics-reporting (for example) If the page exists for an LTS version, the entry for that version shows as LTS. Red admonition.
Versioned page, LTS, in LTS Assistance Support https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/v23.2/diagnostics-reporting (for example) If the page exists for an LTS version, the entry for that version shows as LTS. Red admonition.
Versioned page, LTS, EOL https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/v23.1/diagnostics-reporting (for example) If the page exists for v23.1 and another version, v23.1 will be labeled as LTS and other entries do not. Red admonition.
Unversioned page (Release index) https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/releases/. LTS releases have (LTS) with a link to the Release Support Policy.
Unversioned page (Homepage) https://deploy-preview-18661--cockroachdb-docs.netlify.app/docs/ Unchanged by this PR.

To test the purple admonition for the terminal maintenance phase, you can set the date to 2024-11-13 and check a 23.1 version of a page.

Copy link

github-actions bot commented Jun 17, 2024

Files changed:

  • src/current/_data/alerts.yml
  • src/current/_data/releases.yml
  • src/current/_includes/corestyle.scss
  • src/current/_includes/unsupported-version.md
  • src/current/_includes/version-switcher.html:
    • Warning: include not used in any version-switcher.html file or include
  • src/current/releases/index.md

@mdlinville mdlinville requested a review from mikeCRL June 17, 2024 23:45
Copy link

netlify bot commented Jun 17, 2024

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit 5eaf710
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-interactivetutorials-docs/deploys/66ad641ecf611a0008e2699c

Copy link

netlify bot commented Jun 17, 2024

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit 5eaf710
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-api-docs/deploys/66ad641e1d61f900080a1cc0

Copy link

netlify bot commented Jun 17, 2024

Netlify Preview

Name Link
🔨 Latest commit 5eaf710
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-docs/deploys/66ad641e37083f000890db29
😎 Deploy Preview https://deploy-preview-18661--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@ebembi-crdb ebembi-crdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
Nothing seems breaking, have we tested it?

@mdlinville
Copy link
Contributor Author

LGTM! Nothing seems breaking, have we tested it?

Yes, I have tested it during implementation, but I'm hoping others will too. Some suggestions:

  1. Validate that the Releases index still correctly shows LTS details now that it is looking to versions.csv rather than release.yml.
  2. Validate that the version switcher correctly shows LTS status on versioned LTS pages.
  3. Validate that the 23.1 LTS admonition now shows as a green tip instead of a red warning.
  4. Validate that this doesn't break the functionality that was just rolled out in [DOC-10557] Fix LTS date logic bug and 23.1 TOC #18667 (23.1 should show the LTS admonition on all pages, not just the What's New page).

Copy link
Contributor

@mikeCRL mikeCRL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • On the Releases page, all releases in the 23.2 table have "(LTS)" back through the first alpha.
  • The dropdown shows (LTS) next to 24.1 and 24.2 when each is the selected version. I believe that is incorrect.
  • I am seeing a red warning when viewing 24.1 and 23.2 pages (where the text correctly shows that maintenance support has ended but assistance is still active, per the 'today' date in the PR—LTS assistance in the case of 23.2). I believe these should now be purple?
  • What case should be green, if any? How can I test that?

src/current/_includes/unsupported-version.md Show resolved Hide resolved
@mdlinville
Copy link
Contributor Author

  • On the Releases page, all releases in the 23.2 table have "(LTS)" back through the first alpha.

Should be fixed.

  • The dropdown shows (LTS) next to 24.1 and 24.2 when each is the selected version. I believe that is incorrect.

Should be fixed.

  • I am seeing a red warning when viewing 24.1 and 23.2 pages (where the text correctly shows that maintenance support has ended but assistance is still active, per the 'today' date in the PR—LTS assistance in the case of 23.2). I believe these should now be purple?

Nope, the terminal phase is still red, as per Shannon.

  • What case should be green, if any? How can I test that?

None should be green -- I mention this right below the screenshot showing green.

@mdlinville
Copy link
Contributor Author

The "Everything showing as LTS" bug should actually be fixed now, in this PR.

Copy link
Contributor

@mikeCRL mikeCRL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mdlinville
Copy link
Contributor Author

mdlinville commented Jul 31, 2024

There was some debug output present, now fixed.

It's sad, but we need to redo the looping logic from the Linux tab in the Mac tab. Fixed. Also moved the "LTS" over to the first column to align with the Linux tab.

The reason the Notes column is there is because in v22.2 and v23.1, the contents of all rows are not the same. I will need to conditionalize the # of columns based on the version number to remove them. It's do-able, just adds a bit more complexity to the upkeep of the page.

Let me summarize what I did to fix the Docker tab:

  1. Conditionalize the intro para to show only before the Production section, not for testing releases.
  2. In the intro text, for versions where all Docker images are multi-platform, state that. For mixed versions, retain the explanation about Intel vs multi-platform. For pre-ARM versions,
  3. Show the Notes column only for versions with both GA and pre-GA ARM support (v22.2 and v23.1)
  4. In the Notes column, don't print Intel because it's implied and also covered in the Docker intro.
  • For major versions with an LTS, note that LTS is displayed through the first non-experimental version.

Fixed. I needed to re-initialize some variables in the Docker loop.

  • For v23.1 Production:

    • Row with "Available only for select CockroachDB Cloud clusters" is missing a fourth cell.

It's actually not, it's a colspan. I tested locally after designating 23.1.24 as Cloud-only:

Screenshot 2024-07-31 at 2 05 42 PM

* LTS is listed back through 23.1.13 instead of 23.1.12

I can't reproduce this. Verified in versions.csv that 23.1.11 is listed as the last GA patch and 23.1.12 as the first LTS patch, and here is how it looks with a local build:
Screenshot 2024-07-31 at 2 08 46 PM

  • For Testing releases, can we leave out the GA/Experimental mentions? Perhaps leave it blank? Better to leave "Testing" be the only characterization than to use "GA" there, which is defined as production ready.

I've minimized it, but I am pretty sure I should not remove Experimental from the versions for which ARM actually was Experimental. It's only still listed in v22.2 and v23.1, which had a mix. We need to leave that in there so that customers don't think ARM was supported prior to v22.2.17, v23.1.12, or v23.2.0, including the testing releases leading up to v23.2.0.

Copy link
Contributor

@mikeCRL mikeCRL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mdlinville mdlinville force-pushed the DOC-10431 branch 2 times, most recently from e87dc47 to d53ba41 Compare August 2, 2024 22:53
@mdlinville mdlinville enabled auto-merge (squash) August 2, 2024 22:57
@mdlinville mdlinville merged commit a80267f into main Aug 2, 2024
7 checks passed
@mdlinville mdlinville deleted the DOC-10431 branch August 2, 2024 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants