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

Developers Meeting on Weds, Nov 8, 2017

 

Today's Meeting Times

  • DSpace Developers Meeting / Backlog Hour: 20:00 UTC in #duraspace IRC or #dev-mtg Slack channel (these two channels sync all conversations)
    • Please note that all meetings are publicly logged
    • WARNING: Once your region exits daylight savings time, this meeting will be one hour earlier for you! Be sure to double check what time 20:00 UTC is in your region.

Agenda

Quick Notes / Reminders

  • DSpace 7 Working Group: Next meeting is TOMORROW, Nov 9 at 15:00 UTC (11:00am EDT) in Google Hangouts. See wiki page for meeting details and past meeting notes.
    • DSpace 7 UI Mockups - Watch this page for UI/UX mockups that are currently under discussion, etc.
  • DSpace Entities Working Group: Next meeting is Weds, Nov 22 at 15:00UTC (10:00am EST). See wiki page for meeting details and past meeting notes.

Tim Donohue has some upcoming travel and will be out the following days in November:

  • Nov 13-17 : Travel (at DuraSpace staff meetings). Will be checking email occasionally.
  • Nov 20: Vacation
  • Nov 23-24: USA Thanksgiving holiday


Discussion Topics

  1. (Ongoing Topic) DSpace 7 Status Updates for this week

    1. Team is currently concentrating on building out search functionality & submission functionality
    2. Refactoring of submission configs notes at Configuration changes in the submission process
  2. DSpace High Priority Tickets

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

       Click here to expand...

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

    2. Need Code Review, Flagged for Release

       Click here to expand...

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

  3. Other Tickets needing discussion / attention? (Please feel free to add any you wish to discuss under this topic)
  4. Ongoing discussion topics:
    1. Updating code style & validating via CheckStyle : Code Style Guide (WIP)
    2. 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: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java
  5. 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:

     Click here to expand...

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

  2. Newly created tickets this week:

     Click here to expand...

    Key Summary T Created Assignee Reporter P Status
    Loading...
    Refresh

  3. Old, unresolved tickets with activity this week:

     Click here to expand...

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

  4. Tickets resolved this week:

     Click here to expand...

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

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

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P
    Loading...
    Refresh

Meeting Notes

Meeting Transcript