Bug is less,

[ac_roma]

Yeah, but Acyd hasn't been to work all week (I presume).

I was at work the whole week. Today is the first day off. I am mostly at work.

i hope now WhiteWolfSix know why i call him acyed

[WhiteWolfSix]

release rc1 and you are free to go off for few days.

naive

[lodp]

Yeah, but Acyd hasn't been to work all week (I presume).

I was at work the whole week. Today is the first day off. I am mostly at work.

release rc1 and you are free to go off for few days.

sounds like Acyd Burn's boss posting there

[WhiteWolfSix]

Yeah, but Acyd hasn't been to work all week (I presume).

I was at work the whole week. Today is the first day off. I am mostly at work.

i hope now WhiteWolfSix know why i call him acyed

[Highway of Life]

List of guys for shooting:

• dark/Rain
• Highway of Life
• John Hjorth
• Lastof

I was at work the whole week. Today is the first day off. I am mostly at work.

Wow! some kind of work-place!! 8O Nice!

[Lastof]

Yeah, but Acyd hasn't been to work all week (I presume).

I was at work the whole week. Today is the first day off. I am mostly at work.

Ah. I assumed that since you we're bug fixing all the time you weren't at work.

Then again, I spent too much time this week looking at the bug tracker. So, at least you were doing something useful at work.

[Nicholas the Italian]

RC isn't just two letters put together, they stand for Release Candidate. It means the developer has a product they think is perfect (well maybe not perfect) and ready for release. You don't want to treat Release Candidates the same as betas.

You're right, in theory. Reality here is quite different.
The big difference between betas and RCs is that the former are not supported. The "review later" bugs will be fixed for the next release, so we can suppose there will be a RC2; as you know, delivering an RC knowing that there will be another RC defeats the definition of "(Official) Release Candidate".
I think the reasoning behind releasing RC now is this:
1) the software should be stable enough to be used live without causing major havoc (at least, that's what we hope);
2) having more people using it in real environments can help spotting the remaining issues;
last but not least, 3) if we wait any longer we'll have to keep hearing those complaining etc., and worse, if we release another beta we may get our cars burnt, and I still have to finish paying mine, so that's not a big deal.
Therefore, expect a RC2, and maybe even a RC3. (Of course, there's the remote possibility that I might also happen to be somewhat wrong. )

Ah, an update is in order.
5 new
5 reviewed
2 "fix in progress" (one started Nov 28 the other Mar 29, so not sure what they're going to do with these)
12 total
I dismiss the "review later" ones (49) as they practically don't count now.

[marinedalek]

...and in 10 years we should get the Gold version

[Lastof]

I feel we should count the two Fix In Progress that have been there for ages as Review Later. Same goes for two of the Reviewed bugs, #9855 and #9589, since they have both been there over a month.

It would make the counting nicer, since I don't think these will get done before RC1.

[Schumi]

I feel we should count the two Fix In Progress that have been there for ages as Review Later. Same goes for two of the Reviewed bugs, #9855 and #9589, since they have both been there over a month.

I don't think so for #9589. It has severity set to high and Acyd Burn just said this about it today:

http://www.phpbb.com/bugs/phpbb3/ticket ... et_id=9589

This is quite critical...