https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16840
Bug ID: 16840
Summary: URLs for old releases are broken with every new
release
Change sponsored?: ---
Product: Project Infrastructure
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Project website
Assignee: [email protected]
Reporter: [email protected]
I'm working up a nice CentOS 7 ansible role that builds Koha from the tarball
release. The way you shuffle tarball upon release makes automating koha builds
more difficult than it has to be, and is user hostile.
When you move tarballs under old releases, you don't offer a redirect to the
new location, instead you return a 404. When you publish content to the web,
you should treat that URL as valid for as long as you have the associated
content. In this case, you still have the content, and you know exactly where
it is. Ideally, you would offer clients a 301 redirect to the new location.
You should only return a 404 when you deleted content or honestly have no idea
what the client is asking for.
This is a general website stewardship issue, and it may not seem like the most
critical thing when you are trying to get a release out the door, so I would be
happy to contribute my expertise and/or time to improve this aspect of release
management for Koha.
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
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/
