Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

Shibboleth Developer's Meeting, 2019-02-15

Call Administrivia

09:00 Central US / 10:00 Eastern US / 15:00 UK / 17:00 FI

Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2019-03-01. Any reason to deviate from this?

60 to 90 minute call window.


Call Details

This week's call will use the Zoom system at GU, see ZoomGU for access info.


AGENDA

Add items for discussion here

Attendees:


Brent

  • OSJ-265 - Getting issue details... STATUS
    • Confirmed by testing that server TLS cert can change during renegotiation.


Daniel

  • Continuing work on ldaptive for IDPv3 and v4


Henri


Ian

  • Uploading Spring Framework 5.x to Nexus
  • Updated Product Platforms to move the v8 platform to historical status. MDA now targeted at Java 11.
  • Java 11 transition mostly complete, bar some possible wrinkles in the way integration tests work
    • These should really be Java 11 projects, but should invoke an appropriate different Java version where appropriate.
  • Next up:
    • Tidying up loose ends under Java 11 (e.g.,  JPAR-133 - Getting issue details... STATUS )
    • Probably  JPAR-132 - Getting issue details... STATUS


Marvin

Nothing to report, just here to get up to speed on v4 development.

Phil

Rod

  • IDP-1121 - Getting issue details... STATUS  and related V4 tidy
  • Plans are to continue tidy and my some backlog in SP and EDS


Scott

  • IDP-1405 - Getting issue details... STATUS
    • Keep an eye out for warnings triggered by our code
  • IDP-1413 - Getting issue details... STATUS
    • Mostly done, old Computed/Stored connectors are being collapsed into a new PairwiseId connector
    • New PairwiseId connector type to allow use of arbitrary backing store

Tom

  • JPAR-102 : continuing work
    • current plan is to attach the checksums and pgp key fingerprint files to the parent POM
      • will allow us to use Maven to sign and deploy
      • plugin config probably should reference a URL which points to the Maven repo
    • working through details of building the seed list from our current Nexus repo
  • Java 11 : integration tests

Other




  • No labels