Re: [ANNOUNCE] Release Candidate Available

[Keith Lynch]

I'll second that. I believe that only the people who are in a situation where they have a.the time b the interest c.and desire to support the community are going to try the RC's and this is a great example of the release candidate system working the way it should do However I think that the RC's should also be versioned and contained in the version name. i.e. myfaces-1.1.1.RC1 They are after all released versions. Hi Zong, not to run into problems like that in the final release is what release candidates and beta builds are for. Werner Zhong Li wrote: suggestion on new version release. I know there are lots of changing sine 1.0.9, so it causes lots of bugs. But I think myfaces team need find a way to deal it. This is my suggestion,My faces team can select clients as a special group which voluntarily join new release update/test group, as return, the group get first response of support and seperate mail list. Before any new version released, you have to pass the group test. Otherwise we have to use patches and nightly build, right now I still use nightly build of version 1.0.9 on our production server, it is really bad for us to make a report to our boss. Regards, Zhong Li On 10/2/05, *Wendy Smoak* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: From: "Sean Schofield" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > There is a 1.1.1 release candidate available. > http://cvs.apache.org/builds/myfaces/release/ There are two reports on the user list that 1.1.1 is causing a previously working app to just display a blank page. (Though they're talking about myfaces-all.jar , and I'm having trouble with the api & impl pair.) All of the example webapps display blank pages on Tomcat 5.0.30 and JDK 1.4.2_09. If it helps at all, I've posted the debug logs from the Shale Use Cases app with 1.1.1 as well as the 20051002 nightly build (which uses the RI): http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleUseCases -- Wendy Smoak