Summary: | Indicate what branches of Koha are supported | ||
---|---|---|---|
Product: | Koha | Reporter: | Mirko Tietgen <mirko> |
Component: | About | Assignee: | Bugs List <koha-bugs> |
Status: | Patch doesn't apply --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | liz, martin.renvoize, wizzyrea |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: |
Bug 16349: Scrape currently supported versions
Bug 16349: Scrape currently supported versions |
Description
Mirko Tietgen
2016-04-25 22:31:57 UTC
Hi, Where were you thinking of putting this information? Cheers, Liz Places that would make sense (I think) are 1. the main page, maybe under the "try it now" button, something like Introducing Koha 3.22 [Try it now] Currently supported branches: 3.22 (stable), latest version 3.22.x 3.20 (oldstable), latest version 3.20.x 3.18, latest version 3.18.x I don't know if we could automatically get the latest version from somewhere, because you probably don't want to change that manually every month, but it would be nice to display it. or 2. the download page, under "Get Koha", instead of the link to the wiki that does not really explain anything related to currently supported versions. What do you think? Hi Mirko, I think this information is kept here: https://koha-community.org/about/release-schedule/ and also there are some words about it here (first paragraph): https://koha-community.org/download-koha/ Surely on that first noted page, it could be more explicitly stated that two to three stable versions are supported with bug fixes, I've added some words to that effect. Needs signoff only because I'd like you to look at what I've done before marking it finished - this bug doesn't need the full QA treatment as it is for the website. Cheers, Liz Created attachment 90713 [details] [review] Bug 16349: Scrape currently supported versions Before patch: Koha -> About -> Server Information - Only the currently running version After patch: - Currently supported versions are listed Are you sure you just want it on the web page and not in Koha itself? Created attachment 91845 [details] [review] Bug 16349: Scrape currently supported versions Before patch: Koha -> About -> Server Information - Only the currently running version After patch: - Currently supported versions are listed Are you sure you just want it on the web page and not in Koha itself? Signed-off-by: frederik chenier <frederik.chenier@inlibro.com> 1) QA tools fail: FAIL Koha.pm FAIL critic # ControlStructures::ProhibitMutatingListFunctions: Got 1 violation(s). OK forbidden patterns OK git manipulation OK pod FAIL pod coverage POD is missing for 'current_versions' OK spelling OK valid 2) Also some wrong capitalization: Currently Supported Versions 3) In my master installation it only lists 19.05 and 18.11 - so only the ones we maintain packages for. But actually, we also maintain 18.05. Should we not list this as well? Since bug 21626 we have the 'current' maintenance team highlighted in the 'Koha team' tab along with the date at which they step down from their roles. Does that cover this perhaps, or should we make it more pronounced somewhere? I think having a list of supported versions could still be nice, we could also use it to display an update recommendation for people running 'end of life' versions. I think we should update this patch to use the dates and versions listed in the yaml files shipped with the code. I don't see a reason to scrape externally for it and add load to the website. I'll have a go at putting something together if no-one beats me to it. (In reply to Katrin Fischer from comment #8) > I think having a list of supported versions could still be nice, we could > also use it to display an update recommendation for people running 'end of > life' versions. I really like the idea of this.. though it could cause some vendors challenges when it becomes clear to users that their version is end of life in the eye's of the community. |