I wasn't criticising you James - if they had been updated and 1.2.5 never
made *release" status then that would have been an issue. The process just
needs changing since we've moved to the new style release mechanism.

Niall

P.S. Having never yet attempted to do a release, I guess 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 agree that is a good idea.
>
> The reason 1.2.5 seems incomplete is because it is.  The release process
was
> halted in-process while the discussions took place and I am not sure where
> we stand right now.
>
> 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.
>
> Thanks
>
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> EdgeTech, Inc.
> 678.910.8017
> AIM: jmitchtx
>
> ----- Original Message ----- 
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: "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 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 whether to *release* it
> > then theres a catch 22 situation.
> >
> > I'd like to change the release-notes.xml so that its just and index
> > page with links to the various release notes for the different
> > versions - that way we could have created a release-notes-1.2.5.xml
> > document and had a link to it and distributed them with the build.
> >
> > Also if we did it that way, then we could build up the release
> > notes as changes are made, rather than having to mess around trying
> > to identify whats happened since the last release.
> >
> > Any objections to this - or alternative proposals?
> >
> > Niall
> >
> >
> > --------------------------------------------------------------------
> > - 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]
>
>
>



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

Reply via email to