This DevMtg has been cancelled. This meeting will resume on Weds, Jan 9 at 15UTC. Have a happy holiday break!
- DSpace Developers Meeting / Backlog Hour: 20:00 UTC in #duraspace IRC or #dev-mtg Slack channel (these two channels sync all conversations)
- Final meeting of 2018. This will be our final meeting of 2018. This meeting will resume on Wednesday, Jan 9 at 15:00 UTC
Friendly reminders of upcoming meetings, discussions etc
If you have a topic you'd like to have added to the agenda, please just add it.
(Ongoing Topic) DSpace 7 Status Updates for this week (from DSpace 7 Working Group)
(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.
- OR2019 Presentation Planning (proposals due on Jan 9)
- See 2018-12-19 DSpace 7 Working Group Meeting agenda for a list of the proposed DSpace workshops/presentations (concentrating on DSpace 7)
- Upgrading Solr Server for DSpace (Any status updates?)
- PR https://github.com/DSpace/DSpace/pull/2058
- DSpace Docker and Cloud Deployment Goals (old) (Terrence W Brady )
- Brainstorms / ideas (Any quick updates to report?)
- (On Hold, pending Steering/Leadership approval) Follow-up on "DSpace Top GitHub Contributors" site (Tim Donohue ): https://tdonohue.github.io/top-contributors/
- Bulk Operations Support Enhancements (from Mark H. Wood)
- Curation System Needs (from Mark H. Wood )
- PR 2180 improves reporting. Ready for review.
- Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
- Quick Win PRs: https://github.com/DSpace/DSpace/pulls?q=is%3Aopen+review%3Aapproved+label%3A%22quick+win%22
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
Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)
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: