Yes, that's essentially what we've been doing. I run the Maven summary summary, and
then cut and paste the ones that matter under the various categories we've set up on
the Release Note page.
On Thu, 12 Aug 2004 02:31:23 -0400, Robert Leland wrote:
> You could use what maven produces when you ty
Niall Pemberton wrote:
I'm going to take a look at doing the release notes later. Do we need 1.2.2
release notes that document the changes since Struts 1.1 or do we just need
release notes with the changes since the Struts 1.2.1 beta?
You could use what maven produces when you type:
mave
The release notes just need to be updated since the last time I did them, probably
last month. That much I should be able to squeeze in. They run back to Struts 1.1. If
1.2.2 goes GA, we can start fresh and incorporate the prior notes by reference.
On Wed, 11 Aug 2004 11:33:40 +0100, Niall Pembe
I'm going to take a look at doing the release notes later. Do we need 1.2.2
release notes that document the changes since Struts 1.1 or do we just need
release notes with the changes since the Struts 1.2.1 beta?
I think they should be the full set since Struts 1.1 since that was the last
GA relea