Community
Participate
Working Groups
I'm sorry for posting the request here - didn't find more appropriate "product". In Eclipse build notes there are links to results, which - lead to latest reports from 2002 (i.e. not actual and not interesting to anyone) - do not show what had happen (which problems) in some important areas, e.g. PDE I'm looking for bug reports, which are claimed to be fixed and I'd like to know if it's a part of nightly/integration build. Quite often I can't find it in Build notes. Would be nice if build notes will include somehow reference to a list of all closed bugs for the build.
Although Platform UI has been particularly lax in this area, I agree that a complete list would be good. Moving to Releng for commenting on the best process for doing this since it affects all teams. Way back in LeapFrog days, team members used to just send one-line emails to the group giving the PR number and description e.g. "Fixed 123456 - UI was broken" For build notes, the build person just collected these into a list.
My only comment would be that the teams should update their build notes as they are the only people in a position to know what bugs where really fixed in a particular build. Perhaps we should have a discussion on the eclipse-dev mailing list about what people want to see in build notes.
Probably should. But not right now. Let's do this early in 2.2.
from eclipse-dev mailing list: "Someone noted in an unrelated bug report that our build notes are formatted quite inconsistently. It was noted, and I have to agree, that this makes them hard to read. There are a few different formats used for the header, although the most common seems to be: Eclipse Platform Build Notes <component> Then the build id/date is different for most build notes, followed by a list of bug fixes or a link to a bugzilla report. I wonder if releng can accept build notes for four common categories and compile them into a report for each component using a standard template. This would also allow to compile and categorize the build notes in different ways in the future. For example you could provide just those build notes relevant to the current build instead of cumulative. The common denominator for the categories seems to be: What's new in this drop Other highlights Known deficiencies Problem reports fixed Also, jdt-ui has three different build notes apparently for different release levels all linked off individual builds. Let's say there is a usability problem with the build notes. Who wants to fix it? Knut"
In the JDT/Core team, each committer is responsible for updating the build notes and for adding an entry when he fixes or when he closes a bug. This works quite well, and since the build notes are part of the build contribution, they always reflect what is part of the build.
*** This bug has been marked as a duplicate of bug 170545 ***
