Developers Meeting on Weds, Aug 16, 2017



Quick Notes / Reminders

Discussion Topics

  1. Tim will be out next Tues / Weds, attending the DSpace User Group meeting at Georgetown. (Terry Brady & Mark Wood will also be at this meeting)
  2. DSpace 6.2 Immediate Release to fix Hibernate issues:

    2. Any other very obvious wins to "dspace-6_x" branch?
  3. Discussion of DB Connections in DSpace 6 (Hibernate) vs DSpace 5. (More 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. This is what we saw in DS-3659, two separate Context objects used the same connection, and one accidentally rolled back the changes of a previous Context (because they were in the same thread).
      2. 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:
  4. DSpace High Priority Tickets

    1. High Priority (Blocker, Critical or Major) and flagged for release

    2. Need Code Review, Flagged for Release

  5. DSpace + Spring: Slack Discussion on whether DSpace codebase should move more towards the Spring way of doing things (e.g. Dependency Injection via beans) or the traditional DSpace patterns (e.g. classloaders with little DI).
    1. This was asked on dspace-devel:
  6. DS-3372 and DS-3587: discussion required, should we add more SQL dialect support? MySQL, MS SQL? Are we ready to support, test and maintain these dialects in the future?
    1. Also asked on dspace-devel:
  7. Other Tickets needing discussion (Please feel free to add any you wish to discuss under this topic)
  8. Reviewing JIRA Tickets or PRs
    1. Please feel free to bring any that need eyes / immediate discussion
    2. JIRA Backlog of "Received" tickets
    3. All open PRs

Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release:

  2. Newly created tickets this week:

  3. Old, unresolved tickets with activity this week:

  4. Tickets resolved this week:

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

Meeting Notes

Meeting Transcript