Skip to end of metadata
Go to start of metadata

Date

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. William Welling 
  2. Andrew Woods 
  3. Brian Lowe
  4. Ralph O'Flinn (star)
  5. Michel Héon 
  6. Huda Khan
  7. Alexander (Sacha) Jerabek
  8. Benjamin Gross
  9. Don Elsborg
  10. Santhosh Kumar Gopalan

Agenda

  1. 1.11.2 patch release
    1. VIVO-1929 - Getting issue details... STATUS
    2. VIVO-1943 - Getting issue details... STATUS
  2. Transition from JIRA to GitHub-Issues?
    1. Potential larger gains to be had with using GitHub Actions to push VIVO Docker images
  3. Working towards 1.12
    1. To be reviewed 
      1. VIVO-1918 - Getting issue details... STATUS
      2. VIVO-1934 - Getting issue details... STATUS
      3. VIVO-1937 - Getting issue details... STATUS
      4. VIVO-1944 - Getting issue details... STATUS
    2. Documentation needed
      1. VIVO-1914 - Getting issue details... STATUS
    3. 1.12 release planning
      1. Email of schedule to vivo-community 
      2. Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
      3. Sprint to test merge of sprint-18n into master: week of Jan 25th
      4. 1.12 release candidate #1: Feb 1st
        1. Two week RC-1 testing period
        2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      5. Do we want the `war` install in 1.12? - VIVO-1443 - Getting issue details... STATUS
  4. Tickets that should be close to merge
    1. VIVO-1652 - Getting issue details... STATUS
    2. VIVO-1734 - Getting issue details... STATUS
  5. Post-i18n priorities
    1. VIVO-in-a-box
    2. Messaging
    3. Moving Scholars closer to core - next steps

Future topics

  1. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be?
  2. Renaming of 'master' branch? (ZDNet, BBC)
    1. Guidance from GitHub 
    2. DSpace has done it
    3. Fedora has done it
    4. Samvera is doing it
  3. Incremental development initiatives
    1. VIVO-1688 - Getting issue details... STATUS
    2. VIVO-1751 - Getting issue details... STATUS
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

  1. Status of In-Review tickets

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

Notes 

Draft notes in Google-Doc 

Actions

  •  



  • No labels