When is an RC not an RC?

[Michael Wood]

On 4 October 2012 01:58, Andrew Bartlett <abartlet at samba.org> wrote:
> On Wed, 2012-10-03 at 08:41 +0200, Michael Wood wrote:
>
>>
>> Although, what's the point of labelling something a "release
>> candidate" if it's not a candidate for a release.  i.e. if it's not
>> ready for release (except for unforeseen bugs.)?
>
> Well, we needed to move on from betas to a must more restricted process,
> and calling them gamma releses just don't have the same ring to
> it :-).

Fair enough :)  I don't really mind what you call it.  My brain just
rebelled against the suggestion to release a release candidate when it
was known that a breaking change would be needed later before the
final release.

I understand that nothing's black and white and that there are pros
and cons to delaying a release candidate for something like this.  So
if this change did not make it into rc3, I would not complain :)

> However, in all seriousness we have two weeks before the next RC, and I
> do expect we will sort this out well before then.  This issue only
> appears to have just come up, and in general we are very happy with the
> state of the release.  Work continues on the list of release critical
> bugs at:
>
> https://bugzilla.samba.org/show_bug.cgi?id=8622
>
> It is a very large codebase, and while we are still making changes, the
> vast bulk of the behaviours really are what we will release with.  It is
> also essentially the same process we will use for 4.0.x releases.

Yes, I understand.  Sorry for throwing in my pointless comment.

-- 
Michael Wood <esiotrot at gmail.com>