Dave, >From my perspective as a user, I don't want to install a version that is not considered release quality. Given the iterations on 2.2, I'd say the earlier release candidates should not have been installed by users, so it was better not to know about them. As a developer, I don't think you want users to be running beta-quality code thinking it is production quality code, you will get a lot of superfluous user email.
I read the roadmap, it looks like 2.3 is going to be released this month. Does that mean that 2.2 is dead, or are there plans to release 2.2 if the present rc5 is accepted? I guess what I am trying to say is users should never install release candidates, only approved releases. Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 12, 2006 10:14 AM To: [email protected] Cc: Noel J. Bergman; Henri Yandell Subject: Re: Roller 2.2-incubating RC3 available I've been sending RC notices only to the Roller-dev list, those notices include the changes made in each RC. Noel and Henri: is there a problem with announcing RC releases more widely? Oscar: here are the RC fix lists: RC3 fix list: ROL-1098: import bookmarks was missing from UI RC4 fix list: ROL-1106: Incorrect RSS channel <link> in site-wide feed ROL-1104: Missing planet jars (due to JSTL 1.1 upgrade) ROL-1103: RSS titles not encoded properly (a regression) RC5 fix list ROL-1108: cannot post immediately after making a post - Dave
