Skip to content

Unify various maintenance policy pages/data? #387

Open
@mjankowski

Description

@mjankowski

RE: this blog post - https://rubyonrails.org/2024/10/15/new-maintenance-policy-and-eol-annouments

There is a website page - https://rubyonrails.org/maintenance -- and also a guides page - https://guides.rubyonrails.org/maintenance_policy.html

Before I open a PR anywhere, some questions/speculation...

  • Is it accurate that as of 2024-10-01 the 7.1.x series is no longer bug-fix supported? (and thus should be removed from that section on maintenance page)
  • Same question re: 6.1.x and security fix support
  • Would it make sense to merge the guides page and website page and redirect one to the other? Seems like the guides page has a more verbose write-up of the same policy, but not the current version support list; while the website page does have the versions and has a stripped down policy description.
  • Are the referenced "one more extra release" referenced in the blog post for 6.1.x and 7.1.x beyond their normal support already done (via the Oct 15 and Oct 23 releases) ... or is there more yet to come?
  • Are we open to re-labeling some of the sections on the website page, and/or some general copy cleanup there? Specifically, I find the repeated "List of currently supported releases" lists -- with different versions in each -- sort of confusing. Upon review, I get it, its referring to the bug-vs-security lists, but it's sort of awkward at a glance. Could see something like "List of bug-fix supported releases" / "List of security supported releases" (or something) helping there.

Will take a crack at this if open to it, but I want to be sure to put it in right spot. Please redirect me if this is better handled elsewhere.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions