In addition to the extra info, I changed the Release Criteria page to
say that the release notes are gating, and that they should be included
in the dist (not just on the website). If anyone disagrees, shout.
Rich
Richard Feit wrote:
Definitely. I'll add the item to the release criteria, and towards
the next release the automation will turn into a task.
Eddie ONeil wrote:
Sure, that seems like a good starting point. We'll also need to put
together something that will help automate the generation of this
report; I'd rather not do it by hand.
:)
On 6/7/05, Richard Feit <[EMAIL PROTECTED]> wrote:
Totally. That's a great template for us. Should we just add this
stuff
to the "known issues" (#3.2) of our release criteria
(http://wiki.apache.org/beehive/V1ReleaseCriteria )?
Eddie ONeil wrote:
Yeah, definitely agree with that. Something like this:
http://incubator.apache.org/derby/releases/release-10.0.2.1.html
On 6/7/05, Daryl Olander <[EMAIL PROTECTED]> wrote:
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
?
