Developers Meeting on Weds, May 5, 2010

Agenda

Any Announcements / Additional Agenda Items?
DSpace 1.6.1 Updates (Kim Shepherd)
- 1.6.1 Open Issues: 1.6.1 Version in JIRA
- What to do about DC-Date bugs? Reschedule some/all for 1.7.0?
  - Related date issues include DS-401, DS-497, DS-553, DS-554
- Updates & what issues need more "eyes" on them?
DSpace 1.7.0 Scheduling (Tim Donohue)
- No volunteer Release Coordinator has come forward
- Proposal: As 1.7.0 is a scheduled, time-based release, we may not need a full-fledged "release coordinator". Instead of a coordinator, we could release 1.7.0 based on which features/fixes are ready & documented and have been deemed "acceptable" by the DSpace Committer Group.
  - Tim can help keep everything running on schedule as we get near release time. However, the actual "coordination" would happen amongst various ad-hoc "feature teams" (of interested developers). Those teams would have to work to meet the required schedule in order to get their proposed feature(s) into 1.7.0.
  - See the DSpace Release 1.7.0 Notes for more details on this Proposal
- Proposed Timeline/Schedule for 1.7.0 : DSpace Release 1.7.0 Notes
JIRA Catch-Up – starting with issue DS-517 (and getting as far as we can).
- Search for recent JIRA Issues

Finalizing release schedule for 1.6.1, tentative schedule for 1.7.0, proposal to release 1.7.0 without an RC (unless one can be found)

Updates on 1.6.1 from Kim
- Code Freeze: Friday, May 14
- Release Date: Friday, May 21
- Re-prioritized some issues – any issues/bugs not fixed by Code Freeze will need to be rescheduled for next release.
1.7.0 Scheduling
- General approval for the release schedule/timeline on DSpace Release 1.7.0 Notes
- General approval for the "committing rules" detailed on DSpace Release 1.7.0 Notes
- Some concerns about not having a Release Coordinator for 1.7.0 yet. But, general agreement that we need to move forward with 1.7.0 either way. If a Release Coordinator volunteer comes forward, great. Otherwise, we need to try and manage to release as a team.
- We hope that Community Advisory Team (CAT) could potentially help handle PR announcements around 1.7.0, if a Release Coordinator is not in place to handle that PR / outreach.
- Some concerns that a December release announcement could be "lost" or "missed" right before the holidays. Agreement that we should announce the release again in January (as a friendly reminder)