...

• The release coordinator is responsible for building the release package and uploading it to SourceForge. See Release Procedure for information on how to do this. At the same time as releasing a file the coordinator should also email dspace-devel, dspace-tech and dspace-general to announce the release and add a news item to the SF project page. See other news items for examples of the format of such announcements.

Tips

• It is never too early to start thinking about the release.
• It is never too early to start talking about the release. People are busy and need reminding.
• Try and create a provisional list of major features as soon as possible, even though it will undoubtedly change throughout the year.
• Engage with the developers and gently push for development and commit timescales. Just talking may help speed the process.
• A commit date for a major feature of one week before the feature freeze is too late, it will inevitably result in a postponement of the feature freeze date. All code needs review and probably rework, developers need to recognise that and plan accordingly.
• Don't be afraid to badger people. It goes with the role and people expect it.
• Don't be afraid to ask for help.