Do they have to be part of the docs?
How about tagging items to highlight in our milestone plans (or having
another set of elements in the same doc so that we can expand and include
images) so that we can just keep a single document and have them pulled
together automatically. This would work just like the help wanted page.
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503 (tieline 969)
Michael Elder <mdelder@xxxxxxxxxx> Sent by: wtp-dev-admin@xxxxxxxxxxx
02/21/2005 05:31 PM
Please respond to
Re: [wtp-dev] What's New
and Release Notes
I think the goal of the CVS approach is
really to build a set of action items that we can combine at the end of
the week into one document for Release Notes. The mailing list is less
proned to a "searchable" action item database like CVS.
I'm less concerned about the details of
the approach, but having some sort of standard will make it easier for
us to compile the items and to release them in a consistent fashion to
Michael Elder <mdelder@xxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx
02/21/2005 03:10 PM
Please respond to
[wtp-dev] What's New and
Has there been any discussion or is there already a formal
plan for a
Release Notes/What's new section on the website or elsewhere?
While we're testing, it seems like it would be valuable
to keep track
of these things for the M3 release to make it as polished as possible.
Could we use Bugzilla to track these items? Perhaps use the "enhancement"
or "trivial" severity and a special header (e.g. "[ReleaseNotes]"
"[WhatsNew]"). Each team could then designate a coordinator to
these and build the relevant notes for release on a WTP-wide basis.
The org.eclipse.wst.doc.isv plugin (and the upcoming
org.eclipse.jst.doc.isv) would be good locations for each of these