Page tree
Skip to end of metadata
Go to start of metadata

Developers Meeting on Weds, June 13, 2018


Today's Meeting Times


Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

Discussion Topics

If you have a topic you'd like to have added to the agenda, please just add it.

  1. OR2018 DSpace talks.  For those who missed OR2018, here's a link to the major updates/workshops related to DSpace.  An OR2018 email to all lists will also be coming in the next day or so.

    1. Talks
      1. DSpace 7 Update talk slides:
      2. Repository Rodeo Panel (a panel where all repository-related projects are represented. Each project provides an overview & recent news)
        1. Slides:
        2. Video:
    2. Workshops / Tutorials
      1. DSpace 7 REST API Workshop slides:
      2. DSpace 7 Angular UI Workshop slides:
  2. (Ongoing Topic) DSpace 7 Status Updates for this week

    1. DSpace 7 Working Group is currently concentrating on building out search, submission, authentication and MyDSpace functionality. 4Science submission/workflow UI (see  video, slides) to be submitted as series of PRs in coming weeks.
    2. DSpace 7 Dev Status spreadsheet:
  3. (Ongoing Topic) DSpace 6.x Status Updates for this week

    1. DSpace 6.3 Release Planning is ongoing. Target release date (was) week of June 11 (after OR2018), in reality just "ASAP once 4.x and 5.x releases are also sorted". There is just one PR sitting with a 6.3 milestone: Ben Bosman has shifted an S3 assetstore fix back to 6.3, so it will need testing / review. The rest of the work is testing and forward porting, and writing announcements, release notes, contributor credits, and the maven / sonatype release itself. Kim Shepherd has shared a draft gist of release notes / announcement text on the DSpace Committers list, would appreciate feedback on major fix highlighting. The contributor list needs updating the day before release.

    2. We need volunteers to release 4.9 and 5.9 so we can backport some important 6.x fixes and release simultaneously with 6.3
  4. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)

    1. DS-3649 - Getting issue details... STATUS
    2. JIRA tickets / PRs marked for 6.3:

Tabled Topics

These topics are ones we've touched on in the past and likely need to revisit (with other interested parties). If a topic below is of interest to you, say something and we'll promote it to an agenda topic!

  1. Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
    1. In DSpace 5, each "Context" established a new DB connection. Context then committed or aborted the connection after it was done (based on results of that request).  Context could also be shared between methods if a single transaction needed to perform actions across multiple methods.
    2. In DSpace 6, Hibernate manages the DB connection pool.  Each thread grabs a Connection from the pool. This means two Context objects could use the same Connection (if they are in the same thread). In other words, code can no longer assume each new Context() is treated as a new database transaction.
      1. Should we be making use of SessionFactory.openSession() for READ-ONLY Contexts (or any change of Context state) to ensure we are creating a new Connection (and not simply modifying the state of an existing one)?  Currently we always use SessionFactory.getCurrentSession() in HibernateDBConnection, which doesn't guarantee a new connection:

Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P Status Fix Version/s

  2. Newly created tickets this week:

     Click here to expand...

    Key Summary T Created Assignee Reporter P Status

  3. Old, unresolved tickets with activity this week:

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P Status

  4. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Assignee Reporter P Status Resolution

  5. Tickets requiring review. This is the JIRA Backlog of "Received" tickets: 

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P

Meeting Notes

Meeting Transcript