Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees

Agenda

  1. Announcements 
    1. Upcoming Sprints
    2. <Your announcement here>
  2. Sprint Preparation (Pre/Mini/Non) Sprint Progress
    1. Review work accomplished this week
      1. Jiras
      2. CTS
      3. Documentation
  3. Review External Content Discussion on the fedora-tech

  4. All API Alignment Issues


  5. Tomcat (and Jetty) Support in 5.x 

Ticket Summaries

  1. Please squash a bug!


  2. Tickets resolved this week:


  3. Tickets created this week:


Minutes

  1. Sprint sign up reminder, if you haven't and you can please sign up.
  2. Sprint Preparation
    1. Ideally if we are focused on testing by the start of the first sprint.
    2. Not a lot has moved on the API test suite this week.
    3. Kevin Ford has done some more work on documentation.
    4. Some guidelines on documentation added at the top.
    5. Various ACL tickets being worked by Danny Bernstein.
    6. Jared Whiklo is experiencing a Shiro error when using mvn jetty:run which is causing Authz to fail.
    7. There is a lot of work in the Authentication realm to chip away at.
  3. Due to the large number of responses possible when handling=copy from a remote server are we opening ourselves up to issues.
    1. 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.
  4. Tomcat/Jetty support
    1. Tomcat 8.0 branch is EOL (move to 8.5)
    2. Do we need to specify a Tomcat version policy in the same vein as the JVM policy?
    3. Perhaps a "This release has been tested with XXX" to notify what testing in a set of JVM containers has been done.
    4. Should there be a page of Tomcat recommendations and add links from any existing Tomcat recommendations to this page?
    5. Might just the System Requirements page is the only location to specify a Tomcat version currently.
    6. Moving forward we will:
      1. Link any found Tomcat versions to the System requirements page to keep versions in a single location.
      2. When publishing a release that it was tested with X version of Tomcat add that information to the Release notes.
      3. Move to using Tomcat 8.5 as the current version of Tomcat for testing and support.

Actions