Community
Participate
Working Groups
(already raised against maintenance builds at 2005-08-17, bug 107177) Sorry for bothering you again, but there is still an issue with completeness and usability of build notes for many Eclipse platform plugins. - completeness means, that one could see what happens in recent build - usability means, that for example one have a link to appropriated bugzilla entry for each change. This is not really a problem which take much time to resolve. It should be simply accepted by all groups as basic feature to communicate with community. The build notes are there to allow others to decide if the build has or not some significant changes in some area and to accept the build or to wait for the next one. If build notes are incomplete or 2 years old, it does not make sense to name it "build" notes and include it to the build notes page. OUTDATED AND NOT USER FRIENDLY: core-expressions (last entry: Mai 7, 2004) compare (last entry: September 23rd 2004) jdt-ui(last entry: March 7th 2006) pde-build(last entry: 3.1 RC4 candidate) pde-ui (last entry: 3.1.2) platform-webdav (last entry: 3.0 RC4) search (last entry: I20060131) team (last entry: September 23rd 2004) text (last entry: February 7th 2006) OUTDATED BUT USER FRIENDLY: platform-core (last entry: 3.1 RC4) NOT USER FRIENDLY BUT UP TO DATE ltk-core-refactoring (bug numbers missing) ltk-ui-refactoring (bug numbers missing) swt (only html links to bugzilla are missing) UP TO DATE AND USER FRIENDLY: compare jdt-core jdt-debug platform-ant platform-debug workbench So please, follow the example of the last 6 groups and made the life for us easier. Thank you!
P.S. The first comment was based on the 3.2RC5 build notes at http://download.eclipse.org/eclipse/downloads/drops/S-3.2RC5-200605191206/buildNotes.php but is valid for all latest build notes (milestone or integration builds).
Understand your frustration. Will investigate post 3.2 release. Some of the other teams non-platform teams have tools that generate release notes automatically from CVS tags.
### A friendly reminder about current state ### I was trying to understand which changes are in the latest 3.2.2 maintenance and 3.3M4 builds, and still see the problems described above. I'm responsible to decide which Eclipse build should be considered as "default" for development and deployed in the lab or for customers and it is impossible or very hard to decide because of incomplete build notes. It is also very hard to evangelize new Eclipse builds without reliable arguments (especially in the company with strict quality policy)... Please please, spread the importance of good build notes to the teams which are still not following excellent example of jdt.core team (I *love* their build notes!!!).
*** This bug has been marked as a duplicate of bug 170545 ***
