Community
Participate
Working Groups
The "old" EMF build system included a "promote" step that uploaded the build (and update site contents) to download.eclipse.org. Another thing it did was generate "release notes" for the build, as a way to publish what's changed in the build since the last promoted build. We need the same/similar capability in order to switch over to Buckminster for EMF builds. The release notes consisted of an RSS feed that included entries (identified by build ID or timestamp) listing the bugs that were address in the build. These were discovered based on a commit comment convention, whereby the bug number was enclosed in square brackets at the beginning of the comment. Each of the addressed bugs in the list included a link to the web-based CVS difference view so that the specific source changes for each bug could be seen. The release notes were made available for each build and also as a whole via the project page.
How was this done in the old EMF system? I'd like to look at the code that did this. Perhaps it can be reused, or at least used as reference.
Detailed information about how this is/was done in the old system can be found at http://wiki.eclipse.org/Search_CVS,_Release_Notes,_Build_News and http://wiki.eclipse.org/Search_CVS#Setup, and the associated scripts they reference.
See also http://build.eclipse.org/modeling/build/schema.php.
