Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Anton Emelianov (Deactivated)

Kelly Drake

Marie Widigson

Kelly Drake

Anton Emelianov (Deactivated)

Martina Schildt

Peter Murray

Christie Thomas

Patrick Roth

Tracy L Patton

Martina Tumulla

Aaron Neslin

Monica Arnold

Darsi Rueda

Natascha Owens

morganm@gvsu.edu

patty.wanninger

Dwayne Swigert

Tom Wilson

Steve Bischof

Karen Newbery

Ann-Marie Breaux (Deactivated)

Jacquie Samples

Charlotte Whitt

Robert Scheier

Jenn Colt

egerman

Goals

Discussion items

TimeItemWhoNotes

Test casesPaulaHolly reports that 42% of the test cases are still unclaimed.  They really need more help. Our high level of community participation in this kind of activity was noted as a huge strength in a recent outside review of FOLIO's health.

Importance of release deadlines and the effect of missing release deadlines on releasesAnton Emelianov

Slide deck:

Widget Connector
urlhttps://docs.google.com/presentation/d/194R5EemQzUEK5aE0_luHpsEyL8A22RDX8kTpBfD5saI/edit?usp=sharing

Feature Development Freeze Dates

Multiple layers

  • Base layers that everyone depends on
  • Okapi/Stripes/RMB/Springway - this freeze needs to happen first
  • Modules feature development freeze - Platform core modules
  • Modules feature development freeze - Platform complete modules
  • Team vs module responsibility matrix - each module and their teams & POs, etc

Any slip at any layer can have negative effect

As work progresses it often happens that SMEs ask for enhancements or corrections to the work that is scheduled.  Some of that is expected but when implementation is near the temptation to add in more can get out of control.  We need to decide which ones are critical for the release.  You need to check in with POs to see that progress is being made.  Implementers should help POs prioritize features in this release.  We need to prioritize fixing something that isn't working correctly over trying to add in little enhancements that are very nice to have but weren't in the original stories.

Kelly - whenever something comes in after the deadline, it pushes something else out.  If a PO says we can't fit something in, we really can't. 

AMB - since Juniper is such a short release maybe we don't introduce new features

Tom - Juniper if more of a catch-up release, maybe we should have one of those each year

Feature Development Freeze Definition

  • We cannot add features after this date
  • All features are passing Definition of Done
  • Only changes to address defects are allowed
  • Release branch is created at this date
  • All defect fixes have to be applied to both release branch and Master
  • Next release period features can be merged from development branches
  • Next release period feature development is expected in Master branch

Crucial Juniper Milestones

  • Apr 23 - Deadline for requests to add new modules to the reference environments
  • May 21 - OKAPI, RMB, Stripes, SpringWay freeze
  • May 28 - Modules feature development freeze Juniper - Platform core modules
  • June 4 - Modules feature development freeze Juniper - Platform complete module - please don't ask for any more features at this point
  • June 18- Module release deadline
  • June 28-July 23 - Juniper release testing and hardening period
  • Aug 2 - release is public







Future topics

Receiving workflow demos deferred until Honeysuckle -

Holly will attend on Apr 13, 20 & 27 to address questions related to pointing exercise with a retrospective early May






Next Meeting
April 6 - Discovery demo - specifically VuFind - for April 6

...