I think you guys are both correct. If users want to help the testing of
RCs then that is fine with us, or if they just want to stay on the
bleeding edge. However, I think that the RC notices should only go to
the roller-dev list and are obviously unsupported releases because they
are meant for testing. We cannot be responsible for users who deploy
RCs on production systems expecting them to be perfect.
Oscar, if you want to continue getting info about RC releases then you
should probably get on the roller-dev list as well.
-- Allen
Tribley William-cwt010 wrote:
Oscar,
Well put. Thanks for your perspective. It is clear on the download pages
what is released and what is candidate, let the sysadmins go for it.
I guess I figure that if I install a release it should be expected to
work without major testing, while a RC should be thoroughly vetted
before turning on to production. One day this may come back to haunt
me...
Bill
-----Original Message-----
From: Oscar del Rio [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 12, 2006 11:29 AM
To: [email protected]
Subject: Re: Roller 2.2-incubating RC3 available
But if we don't test them, bugs would not have been found.
I think it is up to sysadmins if we want to test RC versions on small
sites like ours. We know the difference between RC versions and
released versions and are willing to test them and contribute back with
feedback or patches, even if we are not developers, just admins (and a
user myself).
Of course before any upgrade (RC or release) you should test basic
functionality and the upgrade process by installing the new version in a
test machine.
I agree that large sites might want to wait for stable releases but it
doesn't mean that release candidates should be hidden away.
Even blogs.sun.com is running 2.2 that has not been released yet.
We are happily running 2.2-RC2 because it introduced features and fixed
several bugs of 2.1 that some of our users were not happy about.
