<br><br><div class="gmail_quote">On Wed, Oct 21, 2009 at 1:03 AM, Ken Bass <span dir="ltr"><<a href="mailto:kbass@kenbass.com">kbass@kenbass.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">ryan patterson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Oct 20, 2009 at 4:46 PM, mark <<a href="mailto:markhsa@gmail.com" target="_blank">markhsa@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would agree with this. Users should not be referred to the DEV list on<br>
RC1 IMHO.<br>
<br>
<br>
</blockquote>
<br>
I'm certainly not a developer. But I wont let that stop me from<br>
throwing in my two cents. In my mind a release candidate is unstable<br>
software that is still in development. Chronologically release<br>
candidates come before beta releases (which are also unstable and in<br>
development). So I don't see how you can expect to run a RC or beta<br>
release and not follow the -dev & -commits lists. The textbook<br>
definition of release candidate is practically: "development version<br>
for next stable release".<br>
<br>
</blockquote>
<br></div>
I take the exact opposite view. A release candidate is a version you<br>
want a wider user base to test. The expectation is that there will be<br>
problems but once a release candidate is 'set free', you spend time with<br>
all the various 'support' issues trying to fixup those problems in<br>
preparation for the official release (or the next release candidate).<br>
<br>
A release candidate comes AFTER a beta release. Typically a beta release<br>
is to a select group of beta testers. The release candidate audience is<br>
much wider.<br>
<br>
I would not even go as far as to call a release candidate a 'development<br>
version'. It is more like the final version 'unless major problems are<br>
found by testers'.</blockquote><div><br></div><div>I totally agree with you, and other who have said much the same, 'Release Candidate' means exactly that... its a potential release version if no 'deal stoppers' are found. Release Candidates are intended to have a much wider audience so that nothing major creeps out in the release.</div>
<div><br></div><div>Andrew </div></div><br><br clear="all"><br>-- <br>Head of Software & Technology<br>Convergent Home Technologies Ltd<br><a href="http://www.dianemo.co.uk">www.dianemo.co.uk</a><br><a href="http://www.cascade-media.co.uk">www.cascade-media.co.uk</a><br>
<br>