Re: rc#x vs. firmware v.x
Let's use Firefox as an example to explain this easier, ok?
So they have Alphas (really early versions) first, then Betas and then Release Candidates. When they feel the software is almost there, just about ready to release, they do the first Release Candidate. They know it won't be perfect, but it's stable enough to release and for people to use. It gives you an idea for the final product.
People submit bug reports/fixes/etc. and they incorporate those into it and release another release candidate. People either submit other major bugs found or if it's all minor stuff, they fix those and then release it as a final. So for Firefox 3.0, it went alpha, then a few betas, then RC1, RC2, RC3 and then 3.0... after it's releases, fixes and such become point releases. So it's at Firefox 3.0.4 now I believe.
There's probably some site that explains this much better, but this is just off the top of my head.
"Open is for losers." -A Friend
Bookmarks