...
- Sprint sign up reminder, if you haven't and you can please sign up.
- Sprint Preparation
- Ideally if we are focused on testing by the start of the first sprint.
- Not a lot has moved on the API test suite this week.
- Kevin Ford has done some more work on documentation.
- Some guidelines on documentation added at the top.
- Various ACL tickets being worked by Danny Bernstein.
- Jared Whiklo is experiencing a Shiro error when using mvn jetty:run which is causing Authz to fail.
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2798 - There is a lot of work in the Authentication realm to chip away at.
- Due to the large number of responses possible when handling=copy from a remote server are we opening ourselves up to issues.
- Consensus was returning a 502 Bad Gateway for all non-200 responses from upstream servers, with some additional context on the reason for the error.
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2828
- Tomcat/Jetty support
- Tomcat 8.0 branch is EOL (move to 8.5)
- Do we need to specify a Tomcat version policy in the same vein as the JVM policy?
- Perhaps a "This release has been tested with XXX" to notify what testing in a set of JVM containers has been done.
- Should there be a page of Tomcat recommendations and add links from any existing Tomcat recommendations to this page?
- Might just the System Requirements page is the only location to specify a Tomcat version currently.
- Moving forward we will:
- Link any found Tomcat versions to the System requirements page to keep versions in a single location.
- When publishing a release that it was tested with X version of Tomcat add that information to the Release notes.
- Move to using Tomcat 8.5 as the current version of Tomcat for testing and support.
Actions
- Danny to explore inserting a macro into documentation for Fedora version.
- Send email to community seeing who is interested in reviving OAI
...