Update the release process regarding change log generation [SPR-9740]

[spring-projects-issues]

Sam Brannen opened SPR-9740 and commented

Status Quo

Until now the Spring team has manually maintained the changelog.txt file for each release. Although this results in a change log that represents the most significant changes in a given release from the point of view of the core developers, this process has proven to be somewhat cumbersome. In addition, this information is duplicated both in JIRA and in GitHub commits.

Goal

Automate generation of the change log.

Deliverables

The following deliverables were agreed upon recently by the Core Spring developers.

1. Stop manually crafting entries in changelog.txt
2. Instead, focus on a well crafted "What's new in Spring 3.x" section in the reference manual
3. Update the release process:
   • link to the appropriate "What's new in Spring 3.x" section of the reference manual in changelog.txt
   • link to the online JIRA change log for the 3.x release in changelog.txt
   • include a text version of the JIRA change log for the 3.x release in changelog.txt

---

No further details from SPR-9740

[spring-projects-issues]

Chris Beams commented

Per team discussions at SpringOne 2012, we'll keep up the status quo for the changelog through 3.2 GA, then eliminate it or otherwise automate it starting with 3.3 M1.

[spring-projects-issues]

Phil Webb commented

Link to https://jira.springsource.org/browse/SPR#selectedTab=com.atlassian.jira.plugin.system.project:changelog-panel&allVersions=true

[spring-projects-issues]

Phil Webb commented

Other than add the link to the announcement there is not much to do here.