Developers Meeting on Weds, June 27, 2018

Agenda

Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

• DSpace 7 Working Group: Second Sprint announced (July 9-20), signups at DSpace 7 Community Sprints.  Next meeting is tomorrow, Thurs, June 28 at 14:00 UTC

• DSpace Entities Working Group: Next meeting is TBD.

  • See recent announcement from DSpace Steering regarding Entities work: https://duraspace.org/statement-from-dspace-steering-group-on-the-dspace-7-data-model/
• DSpace Developer Show and Tell Meetings:  Next Show & Tell will be June 26 at 15:00 UTC.

Discussion Topics

If you have a topic you'd like to have added to the agenda, please just add it.

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

   1. DSpace 7 Working Group 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

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

   1. DSpace 6.3 Release is nearly complete.  Announcements going out soon.

3. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)

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 heading 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?

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)

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,fixversions maximumIssues 20 jqlQuery filter=13905 ORDER BY fixVersion DESC, priority DESC serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Newly created tickets this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,assignee,reporter,priority,status maximumIssues 20 jqlQuery filter=13902 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Old, unresolved tickets with activity this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status maximumIssues 20 jqlQuery filter=13906 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13903 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

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

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,assignee,reporter,priority maximumIssues 20 jqlQuery filter=10152 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Meeting Notes

Meeting Transcript

• IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2018-06-27