Today's Meeting Times
Friendly reminders of upcoming meetings, discussions etc
- DSpace 7 Working Group: In the midst of our DSpace 7 Community Sprint 3. Follow along on #dev-sprint
DSpace 7 Entities Working Group: Next meeting is TBA (Next week).
Last week's meeting (including video recording): 2018-09-25 DSpace 7 Entities WG Meeting
- DSpace Developer Show and Tell Meetings: Next meeting is Oct 30 at 15:00 UTC on Docker Updates
If you have a topic you'd like to have added to the agenda, please just add it.
- Sprint #3 is ongoing, no updates to report.
(Ongoing Topic) DSpace 6.x Status Updates for this week
- 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.
- DSpace Release 5.10 Status - Tentative release date on Thursday, Oct 4
- DSpace and Docker#Proposal:SupportMultipleJDKVersions
- Follow-up on "DSpace Top GitHub Contributors" site: https://tdonohue.github.io/top-contributors/
- Fedora developers have voted to not implement "top contributors" at this time. This will be released as DSpace-only initially.
- Follow-up on Curation Task Reporting (PR 2180)
- Brainstorms / ideas (Any quick updates to report?)
- Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
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!
- Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see 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.
- 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
- Should we be making use of
Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)Click here to expand...
Key Summary T Created Updated Assignee Reporter P Status Fix Version/s
Newly created tickets this week:Click here to expand...
Key Summary T Created Assignee Reporter P Status
Old, unresolved tickets with activity this week:Click here to expand...
Key Summary T Created Updated Assignee Reporter P Status
Tickets resolved this week:Click here to expand...
Key Summary T Created Assignee Reporter P Status Resolution
Tickets requiring review. This is the JIRA Backlog of "Received" tickets:Click here to expand...
Key Summary T Created Updated Assignee Reporter P