Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Developers Meeting on Weds, June 27, 2018

 

Today's Meeting Times

Agenda

Quick Reminders

Tim Donohue has some vacation / holiday time coming up in the next few weeks.

  • June 27: Unavailable in the morning. Around in afternoon.
  • July 2-6: On holiday. Will be rarely checking email. Returning to office on July 9.

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. NO MEETING on Weds, July 4. This is a USA Holiday. We will return to our normal schedule on Weds, July 11 at 15:00 UTC.

  2. (Ongoing Topic) DSpace 7 Status Updates for this week.  No major updates this week.

    1. DSpace 7 Working Group (2016-2023) is where the work is taking place
    2. DSpace 7 Dev Status spreadsheet: https://docs.google.com/spreadsheets/d/18brPF7cZy_UKyj97Ta44UJg5Z8OwJGi7PLoPJVz-g3g/edit#gid=0

  3. (Ongoing Topic) DSpace 6.x Status Updates for this week

    1. DSpace 6.3 Release is complete. Woo! Announcements and security advisories have been sent. Thanks to everyone who helped with PRs, testing, reviews and release tasks!

  4. Any interest in folks from this meeting taking part in the next DSpace 7 Community Sprint (July 9-20)?  
    1. Currently, looks like it'll be a small group.  But, this is a great opportunity to learn "hands-on" with support from Sprint Coaches (via Slack and meetings).  Again, we have no availability requirements. Even simply claiming one ticket to work on would be of help.
  5. Now that 6.3 is out the door, we have an opportunity to bring other topics to this agenda.  Any brainstorms/ideas on upcoming topics that are of interest to this weekly meeting?
  6. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
    1. Master ports from 6.3. Kim Shepherd has a Google Sheet with a list of issues that we've had to close to ensure the 6.3 changelog was accurate, but which are still waiting on pull requests for master to be written / merged. As we're working through this list, we should remove the 'port to master' label from the dspace-6.x PR and if possible, edit the JIRA comment to remove the "63_PORT_TO_MASTER" text. The following link gives anyone edit access so please be kind, I trust you all! https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing 
    2. Preparing for 6.4: Another message from Kim Shepherd , who is as sick of 6.x as all of you (smile) We need to move all open JIRA issues with fix version of 6.3 to 6.4, and the sooner we get onto reviewing and merging PRs, keeping on top of ports and documentation and admin tasks etc, the smoother the next bugfix release will be.

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: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java


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)

    key summary type created updated assignee reporter priority status fixversions

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Newly created tickets this week:

    key summary type created assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Old, unresolved tickets with activity this week:

    key summary type created updated assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets resolved this week:

    key summary type created assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

    key summary type created updated assignee reporter priority

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Meeting Notes

Meeting Transcript

 

1 Comment

  1. Terrence W Brady

    The June 27 meeting did not occur due to Slack Connectivity issues.  I encouraged folks to post status updates on this page.


All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.