This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora
+1 408 638 0968
+1 646 876 9923
+1 669 900 6833
812 835 3771
Join fedora-project.slack.com on the "tech" channel
- Danny Bernstein
- Peter Eichman
- Andrew Woods
- Jared Whiklo
- Bethany Seeger
- Ben Pennell
- Kevin Ford
- James Silas Creel
- David Wilcox
- Upcoming Sprints
- <Your announcement here>
- Sprint Preparation (Pre/Mini/Non) Sprint Progress
- Review External Content Discussion on the fedora-tech
All API Alignment IssuesClick here to expand...
- Tomcat (and Jetty) Support in 5.x
Please squash a bug!Click here to expand...
Tickets resolved this week:Click here to expand...
Tickets created this week:Click here to expand...
- 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.
- 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.
- 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.
- Danny to explore inserting a macro into documentation for Fedora version.
- Send email to community seeing who is interested in reviving OAI