[platform-releng-dev] Currrent build notes are important to consuming te

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

Releng has an open bug regarding the
lack of current information in the build notes for many components that
contribute to the SDK.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=142909

Recently, it was updated with the following
comment that I thought I would pass on to the team.  

https://bugs.eclipse.org/bugs/show_bug.cgi?id=142909#c3


### 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!!!).


Since M2, the releng tool includes a
checkbox to update your build notes when you update your map files so it's
very a painless process :-)

See the "Releng Tools" section
of the 3.3M2 Release notes for more information

 http://download.eclipse.org/eclipse/downloads/drops/S-3.3M2-200609220010/eclipse-news-M2.html

thanks,
Kim