I think we want to reward people who are helping us test the non-GA
releases as well, by delinieating the dot-dot changes separately. 
That still gives people who want the whole picture what they need:

  Changes in version 1.2.6:
  * ...
  * ...

  Changes in version 1.2.5:
  * ...
  * ...

  Changes in version 1.2.4:
  * ...
  * ...

and so on (the embedded lists can be links if there's too many bullets
for one big page).

Craig


On Tue, 26 Oct 2004 17:30:29 +0100, Niall Pemberton
<[EMAIL PROTECTED]> wrote:
> This raises another question. Do we want the release notes to be "all the
> changes since the last GA quality release" or "the changes in this version"?
> 
> I'd prefer "all the changes since the last GA quality release" as I think
> thats what users really want to know. If a build doesn't make GA release
> status then we can just copy it over to the next version of the release
> notes and delete it.
> 
> If people agree with that and were just going to push straight on to 1.2.6,
> then we can skip the 1.2.5 release notes and just set up 1.2.6 ones
> 
> Niall
> 
> 
> 
> 
> ----- Original Message -----
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: "Struts Developers List" <[EMAIL PROTECTED]>
> Sent: Tuesday, October 26, 2004 4:35 PM
> Subject: Re: Release/Version Notes
> 
> On Tue, 26 Oct 2004 11:12:51 -0400, James Mitchell wrote:
> > It was my impression that Ted would update the release notes and I
> > was simply putting some of the other pieces together. I am still a
> > newbie to the release process so please be kind.
> 
> I did mean to, James, but I just didn't get to it in time :(
> 
> If I had, I would have just restarted the release-notes.xml page, since
> 1.2.4 was a GA release.
> 
> But I like Nial's suggestion better :)
> 
> I would be happy to do the notes for 1.2.5, in the manner Nial described.
> Then maybe the best thing would be to move onto 1.2.6, since there have been
> some patches applied, and there might be a few more yet this week. I'd also
> be happy to document whatever problem tickets we don't resolve, if that
> would help.
> 
> -Ted.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to