Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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 end-users.
Kind Regards,
Michael D. Elder
Rational Studio / J2EE Tools Development     
Ext: (919) 543-8356
T/L: 441-8356
Monday, February 21, 2005 5:21 PM
To: wtp-dev@xxxxxxxxxxx
cc: wtp-dev@xxxxxxxxxxx, wtp-dev-admin@xxxxxxxxxxx
From: Arthur Ryman <ryman@xxxxxxxxxx>
Subject: Re: [wtp-dev] What's New and Release Notes


I'm all for having a "New and Noteworthy" document for M3. I believe component leads have handled this type of information in the past.

I'm not sure using Bugzilla is the way to go. Why not use the mailing list, and tag the subject with the special headers you propose?

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

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 Release Notes

Extended Team:

     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]" and
"[WhatsNew]"). Each team could then designate a coordinator to collect
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

     Other thoughts?

Kind Regards,

Michael D. Elder
Rational Studio / J2EE Tools Development
Ext: (919) 543-8356
T/L:  441-8356

wtp-dev mailing list

Back to the top