Re: Release/Version Notes

2004-10-26 Thread Craig McClanahan
t; - 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, Jam

Re: Release/Version Notes

2004-10-26 Thread Niall Pemberton
riginal 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

Re: Release/Version Notes

2004-10-26 Thread Niall Pemberton
I'm not even at "newbie" status :-) - Original Message - From: "James Mitchell" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, October 26, 2004 4:12 PM Subject: Re: Release/Version Notes > I also ag

Re: Release/Version Notes

2004-10-26 Thread Ted Husted
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

Re: Release/Version Notes

2004-10-26 Thread James Mitchell
uot;Struts Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, October 26, 2004 10:42 AM Subject: Re: Release/Version Notes +1 On Tue, 26 Oct 2004 15:34:03 +0100, Niall Pemberton wrote: Currently we have a 1.2.5 build that has no details of whats changed in the documentation thats includ

Re: Release/Version Notes

2004-10-26 Thread Ted Husted
+1 On Tue, 26 Oct 2004 15:34:03 +0100, Niall Pemberton wrote: > Currently we have a 1.2.5 build that has no details of whats > changed in the documentation thats included with it.  The problem > with the way release notes currently work is that the release- > notes.xml contains the current release

Release/Version Notes

2004-10-26 Thread Niall Pemberton
Currently we have a 1.2.5 build that has no details of whats changed in the documentation thats included with it. The problem with the way release notes currently work is that the release-notes.xml contains the current release - but since a new build (like 1.2.5) is created before its voted on whe