Developers Meeting on Weds, October 3, 2018

Agenda

Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

...

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

   1. DSpace 7 Development Status spreadsheet

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

   1. 6.4 will surely happen at some point, but no definitive plan or schedule at this time.  Please continue to help move forward / merge PRs into the dspace-6.x branch, and we can continue to monitor when a 6.4 release makes sense.
3. DSpace Release 5.10 Status - Tentative release date on Thursday, Oct 4
4. DSpace and Docker#Proposal:SupportMultipleJDKVersions
5. Follow-up on "DSpace Top GitHub Contributors" site: https://tdonohue.github.io/top-contributors/
   1. Fedora developers not interested in extending this for their stats.  This will be released as DSpace-only initially.
6. Follow-up on Curation Task Reporting (PR 2180)
7. Brainstorms / ideas (Any quick updates to report?)
   
   1. Bulk Operations Support Enhancements (from Mark H. Wood)
   2. Curation System Needs (from Terrence W Brady )
      1. PR 2181 implements per-run task parameters.  Ready for review.
      2. PR 2180 improves reporting.  Needs a little more testing
8. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
   1. Quick Win PRs: https://github.com/DSpace/DSpace/pulls?q=is%3Aopen+review%3Aapproved+label%3A%22quick+win%22

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 

...