Versions Compared

Key

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

Developers Meeting on Weds, Sept 27, 2017

 

Info
titleToday's Meeting Times

Agenda

Quick Notes / Reminders

  • NEXT DSpace 7 UI MEETING: TOMORROW, Sept 28 at 15:00 UTC (11:00am EDT) in Google Hangouts

Discussion Topics

  1. DOI field discussion. Where do we store DOIs going forward? (dc.identifier.doi?) 

    1. See this #dev Slack discussion on Sept 20: https://dspace-org.slack.com/archives/C3SG47SGY/p1505923323000280

  2. Terrence W Brady's work with DSpace 6 + Codenvy: https://github.com/terrywbrady/dspace-on-codenvy/blob/master/README.md

  3. DSpace High Priority Tickets

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

      Expand

      Jira
      serverDuraSpace JIRA
      columnskey,summary,type,created,updated,assignee,reporter,priority,status,fixversions
      maximumIssues20
      jqlQueryfilter = 13904 ORDER BY fixVersion DESC, priority DESC
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


    2. Need Code Review, Flagged for Release

      Expand

      Jira
      serverDuraSpace JIRA
      columnskey,summary,type,created,updated,assignee,reporter,priority,status,fixversions
      maximumIssues20
      jqlQueryfilter=13905 ORDER BY fixVersion DESC, priority DESC
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Other Tickets needing discussion / attention? (Please feel free to add any you wish to discuss under this topic)
  5. Ongoing discussion topics:
    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: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java
  6. 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:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,assignee,reporter,priority,status,fixversions
    maximumIssues20
    jqlQueryfilter=13905 ORDER BY fixVersion DESC, priority DESC
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Newly created tickets this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,assignee,reporter,priority,status
    maximumIssues20
    jqlQueryfilter=13902
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Old, unresolved tickets with activity this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,assignee,reporter,priority,status
    maximumIssues20
    jqlQueryfilter=13906
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13903
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


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

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,assignee,reporter,priority
    maximumIssues20
    jqlQueryfilter=10152
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Meeting Notes

Meeting Transcript