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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Developers Meeting on Weds, November 21, 2012

Agenda

Regular Items

  • Forgoing JIRA review for now to spend time on 3.0 & Testathon. Specific JIRA tickets can be brought up as needed.
  • Reminder: DSpace Committer & DCAT joint meeting on "DSpace Future Directions" discussions (which have been going on with DSpace Sponsors over the last month). Try to attend one of these meetings:
    • Tues, Nov 20 at 10:00 am EST (15:00 UTC), OR
    • Weds, Nov 28 at 4:00 pm EST (21:00 UTC)

Discussion Topics

  1. 3.0 Release
    1. List of unresolved bugs in 3.0
    2. Discuss release date (tentative for Nov 27) & possibly finalize
    3. Split up final Release Tasks (see below
  2. 3.0 Outstanding Tasks
    • Squash any last tickets or reschedule ones that can be
    • Finalize release date
    • Release language packs (dspace-api-lang & dspace-xmlui-lang), preferably one day before final release.
    • Final updates to Documentation

      • IMPORTANT: Ensure the "Preface" page is fully updated for 3.0 (Tim did some updates before 3.0RC2, but it needs a second look)

      • Final check of Install & Upgrade Documentation

    • Export Documentation to PDF & commit to GitHub
    • Update all README, LICENSE* files in GitHub
    • Perform actual 3.0 Release (Hardy Pottinger volunteered)
  3. Other topics?

Additional Ongoing Topics

  1. How can we "catch up" with JIRA Backlog?
    • Do we need to "split up" the tickets & do quick reviews on our own? Or perhaps just split up tickets & do a very quick ranking & schedule ones with patches for 3.0?
    • Perhaps we schedule a "JIRA Backlog Bash" event (via IRC or similar) where we work together to decrease the backlog over a few days or a week (think of this like a "Test-a-thon" but instead we'd be working to just clear out the backlog as best we can).
  2. Brainstorming Features/Changes for future. Can we work towards development teams around any of these projects?

Individual Status Updates

If you have status items to report, please enter them below at least 1 hour before the meeting starts.

Meeting Notes

Meeting Transcript

Action Items

(Action items go here, if any)

  • No labels