https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21626
--- Comment #36 from Marcel de Rooy <m.de.r...@rijksmuseum.nl> --- (In reply to Martin Renvoize from comment #32) > So, how about I add a page to koha-community.org something along the lines: [...] > And link to it from the koha about page as part of these enhancements.. I'm > also tempted to add in the dates a cycle takes place on the about page so > that we clearly show if the 'current' maintenance team is no longer current > if a library isn't updating regularly. If I would be using say 17.11.08, I would see the release team of 17.11 (which is fine) and since .08 normally means that we are in the second maintenance cycle, I might see the second RMaint and the release team of 18.11, right? But since I did not upgrade, that info is already out of date. No sense in contacting these individuals. Imo showing two teams is confusing and hard to explain. If you are in say 18.11 QA team, you will be credited for that on a 18.11 about page, and not on the older versions. Should we use the phrase "Original release team"? Remove the maintainers from that section and separately list all maintainers for that version (say 17.11). System date could indeed tell you if the last maintainer is still in function and if the version is even maintained (assuming three cycles). I think we should postpone this to 19.11 btw. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
