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

Meeting Schedule and Attendance

DSpace Developer meetings are a time when Committers and interested Developers can discuss new software features, upcoming releases of DSpace software, and generally plan out the roadmap of DSpace. All meetings are public. We welcome anyone and everyone to attend, speak their opinions or just listen in on the discussions. Please note that we archive all discussions (see Meeting Archives), as a service for those who are unable to attend.

DSpace Developer meetings take place on the following schedule:

You can also subscribe to the meeting schedule via the DuraSpace Public Events Calendar (iCal, RSS Feed).

Meeting topics often include:

  • Recent updates on upcoming DSpace releases, bug fixes or features
  • Reviewing of recent reported issues/bugs/feature requests (see JIRA Cleanup Sessions for more info)
  • Occasionally we vote or make decisions on upcoming DSpace technology plans/roadmap (see Developer Voting Procedures for more info)

If you are unable to attend a meeting, please feel free to add your own notes/comments to the meeting's wiki page.

Developers Meeting on Weds, Oct 18, 2017

 

Today's Meeting Times

Agenda

Quick Notes / Reminders

  • DSpace 7 Working Group: Next meeting is TOMORROW, Oct 19 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 Friday, Oct 27 at 15:00UTC (11:00am EDT). See wiki page for meeting details and past meeting notes.

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. General support for movement towards code coverage tools, ErrorProne and CheckStyle on "master"
    3. DSpace 7 REST Testing Framework

      1. https://github.com/DSpace/DSpace/pull/1866
      2. Example test of /browses endpoint: https://github.com/atmire/DSpace/blob/31e28563b0e9bc44478e5cc7010c2fa72b667cb4/dspace-spring-rest/src/test/java/org/dspace/app/rest/BrowsesResourceControllerTest.java
  2. Updates on Code Mgmt Tools on "master" (e.g. Code Test Coverage, ErrorProne, CheckStyle, etc).

    1. (tick) ErrorProne now enabled on `master`  DS-3712 - Getting issue details... STATUS  and https://github.com/DSpace/DSpace/pull/1861
    2. Enabling Test Coverage reports?  DS-3711 - Getting issue details... STATUS  and https://github.com/DSpace/DSpace/pull/1865
    3. Code Style / CheckStyle:
      1. Code Style Guide (WIP) : Early notes on DSpace code style & how it compares with a few other projects (namely Google and Fedora Commons)
  3. 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

  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:

     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

 

Meeting Archives

Notes and Transcripts from all recent Developers Meetings are available off of the Developer Meeting Archives page.