On Mon, Oct 12, 2009 at 3:31 PM, Simon Laws <[email protected]> wrote: > An observation (which doesn't affect my vote) on the current Maven > Bundle plugin release is that the RELEASE_NOTES seem somewhat erratic > in the amount of detail included from release to release. We should > try and have a standard form for these so we know what to do. > Especially as we are starting to have more separate releases. > > TUSCANY-???? - details about the change > > Seems simple and effective. > > Begs the question about whether we should always have a JIRA number to > track changes we make. If people don't want to do that (I'm easy > either way) then a simple NO-JIRA or similar would distinguish these > changes so the reader doesn't have to guess one way or the other. > > Regards > > Simon >
The previous release of the bundle plugin had no release notes which isn't ideal, but do we really need to fix that with a ridgid process? Many commits don't have an associated JIRA, or often new function will be added over multiple commits. Its also going to depend a bit on the type of release, eg the recent SCA 1.5.1 release was a maintenance release of a relatively stable branch so most commits had JIRAs, the SCA 2.0-M3 release had few JIRAs and it seems fine to me to just have high level bullet points in the release notes. ...ant
