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 2, 2017
Today's Meeting Times
- DSpace Developers Meeting / Backlog Hour: 20: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 3 at 15:00 UTC (11:00am EDT) in Google Hangouts
- DSpace 7 Working Group - Watch this page for initial ongoing updates on meetings, etc.
Discussion Topics
DSpace 6.2 Immediate Release to fix
DSpace 6.3? Release Planning: A few main options for the 6.2 were discussed last week (http://irclogs.duraspace.org/index.php?date=2017-07-26)
- A formally planned 6.3 release. This would necessitate a 6.2 Release Team (ideally of 2 or more volunteers), one or more Release Candidate(s), possibly a mini-Testathon. It'd have the advantage of providing a more thorough bug-fix release, but would require more effort to achieve this.
- An ad-hoc, quick 6.3 release. This would essentially be more like 6.1 (but less large in size). We'd scope 6.2 to a "major bug fix" release, and just fix the major bugs discovered in 6.1 (ideally after further testing by DCAT or similar). It'd have the advantage of being (likely) more rapid release (hopefully allowing developers to work in parallel on 7.0), but it may not be as thorough.
- A quick 6.3 with a formally planned 6.4: This is a combo of the above approaches. It'd provide the benefits of a quick 6.2 release, but it'd necessitate finding volunteers to manage a 6.3 (perhaps later in the year, timeline TBD).
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-02