One thing I would add, is a release description. This would describe the overall goals of the release (feature work, bug fix work, etc). In addition, it would be nice if each release had a bit of a road map for the expectations and time frame is for the next release in the line. In addition, if the release is a branch from some release, the relationship of the release with the branches should be described.
On 6/7/05, Eddie ONeil <[EMAIL PROTECTED]> wrote: > Seems that it should contain all of these. At the very least, bugs > / issues addressed in the release and known issues should go into some > sort of release note (IMHO). Not sure how new features should be > described -- I'd be fine with those being addressed in the same > location under some sort of a different section. > > Eddie > > > On 6/7/05, Richard Feit <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Q: Now that our first (milestone) release is out, what should future > > Release Notes contain? > > > > - high-level description of new features > > - bugs/issues addressed in the release > > - known issues > > > > ? > > >
