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.
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)
Action Items
Announce 1.6.1 Release Date and Tentative Release Schedule for 1.7.0