Community
Participate
Working Groups
3.3 M2 The new tool which can create the build notes is cool but it is a problem for us that it is integrated into the Release command and that it can only update one single build notes file. Reason: our release engineer does the build input for several components at once: Platform Search, Platform Text, JDT Text and JDT UI. We either need a way to specify which project belongs to which build notes file (e.g. in the map file) or we should be able to call the build notes tool separately, so that each component can update its build notes before passing over to the release engineer. The automated solution would be preferred but as a first quick solution a separate menu entry that allows us to just create the build notes would be great.
Re-assigning, since Aaron is gone.
In conjunction with bug 170545 do we need to consider a mapping file in the common build notes folder (plugin->buildnotes file)? Or would it be enough to allow .map files to define their build file, give us one build notes file per map? We could still allow multiple maps to be condensed into one build notes file. I'm not sure which would be technically more difficult. PW
We should not let bug 170545 hold in this one. I suggest we add a new mapping file called org.eclipse.releng/buildnotes.mapping which has entries of the form: <plug-in name>=fullPathOfBuildNotesFile e.g.: org.eclipse.text=/org.eclipse.ui.editors/buildnotes_text.html If the mapping file does not contain a mapping for a plug-in then we fall back to the current behavior i.e. we use the file specified in the commit UI as it is currently done. This way the Releng plug-in behaves like before and only those who need a mapping need to add entries to the new mapping file. Should bug 170545 be realized at some point we can simply update the mapping file. What do you think? If you agree on this I'll work on that tomorrow as part of my freestyle RC2 testing.
With the move to Git, this tool isn't in active use anymore for anything other than copyright updates. I'm going to close this bug as we have no plans to address it.
