Closed SansGuidon closed 1 week ago
This was fixed in https://github.com/shaarli/Shaarli/commit/8d7c85e05c839ae4b8c8c9999eb6413d499bc6f6 but is not part of any release yet. We should at least address some of these issues https://github.com/shaarli/Shaarli/milestone/35 before making a new release.
Should, but is it a technical requirement? It's really up to the CI/CD strategy you define but the general trend and expectation imho for such productivity tools is to continuously ship features and fixes through continuous intermediate/minor version bumps. So unless there is an obvious reason (breaking changes? coupling?) to not ship, it's also good to release whatever can already improve users experience? blocking some improvements which are as old as the one you linked (11 months old) seems a bit counter productive? Some of the issues mentioned and attached to 0.14 are as several years old. I would encourage to ship as often as possible.
You are right -> https://github.com/shaarli/Shaarli/issues/2105
Hi, While opening my instance
/admin/tools
page, whenever I click onCommunity and related software
it opens a broken link at https://shaarli.readthedocs.io/en/master/Community-and-related-software/