...
- Help keep code development around a release organized (DSpace JIRA is a great resource for keeping organized)
- e.g. Ensure each new feature or bug fix has a developer assigned to it
- e.g. If a developer needs help/feedback, help locate that help/feedback from the Committers or the community
- Help communicate information about the Release to DSpace Community
- Report on release status updates during DSpace Developer Meetings
- Ask for additional help/support when a release requires it
...
- Work with the committer group to find volunteers to take patches, claim PRs, code review / test them, and commit them to SVN.merge into the codebase
- Determine a feature freeze date. In a normal release cycle, there will hopefully be a constant influx of patches waiting to be rolled into the relevant release. The feature freeze date, therefore, need not be a long way in advance. It's useful if the date is a Friday, as this allows trailing time-zones to catch up before work in earnest can start on code integration on the Monday.
...
- The release team is responsible for building the release package and uploading it to SourceForge. See Release Procedure for information on how to do this. The release team should also email dspace-devel, dspace-tech and dspace-general to announce the release.
...