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, Aug 9, 2017
Today's Meeting Times
- DSpace Developers Meeting / Backlog Hour: 15:00 UTC in #duraspace IRC or #dev-mtg Slack channel (these two channels sync all conversations)
- Please note that all meetings are publicly logged
Agenda
Quick Notes / Reminders
- NEXT DSpace 7 UI MEETING: TOMORROW, Aug 10 at 15:00 UTC (11:00am EDT) in Google Hangouts
- DSpace 7 Working Group (2016-2023) - Watch this page for initial ongoing updates on meetings, etc.
Discussion Topics
DSpace 6.2 Immediate Release to fix Hibernate issues:
- Any other very obvious wins to "dspace-6_x" branch? https://github.com/DSpace/DSpace/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aopen%20base%3Adspace-6_x%20
- Discussion of DB Connections in DSpace 6 (Hibernate) vs DSpace 5. (More notes at DSpace Database Access)
- 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.
- 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.- This is what we saw in DS-3659, two separate Context objects used the same connection, and one accidentally rolled back the changes of a previous Context (because they were in the same thread).
- 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 useSessionFactory.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
DSpace High Priority Tickets
High Priority (Blocker, Critical or Major) and flagged for release
Need Code Review, Flagged for Release
- DSpace + Spring: Slack Discussion on whether DSpace codebase should move more towards the Spring way of doing things (e.g. Dependency Injection via beans) or the traditional DSpace patterns (e.g. classloaders with little DI).
- This was asked on dspace-devel: https://groups.google.com/d/msg/dspace-devel/oBWibfQUXzI/y05K-wpLAgAJ
- DS-3372 and DS-3587: discussion required, should we add more SQL dialect support? MySQL, MS SQL? Are we ready to support, test and maintain these dialects in the future?
- Also asked on dspace-devel: https://groups.google.com/d/msg/dspace-devel/UfTU7AFZjs0/UOgiSnJKAgAJ
- Other Tickets needing discussion (Please feel free to add any you wish to discuss under this topic)
- Reviewing JIRA Tickets or PRs
- Please feel free to bring any that need eyes / immediate discussion
- JIRA Backlog of "Received" tickets
- All open PRs
Ticket Summaries
Help us test / code review! These are tickets needing code review/testing and flagged for a future release:
Newly created tickets this week:
Old, unresolved tickets with activity this week:
Tickets resolved this week:
Tickets requiring review. This is the JIRA Backlog of "Received" tickets:
Meeting Notes
Meeting Transcript
IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2017-08-09
1 Comment
Terrence W Brady
As a follow up to today's meeting, I created a first draft proposal related to Active Branch Cloud Instances: Proposal: Create Cloud Instances for DSpace Active Branches