Sorry to be pedantic but I think it's important in this case... RC's should NOT be the serious bug finding stage!!! Betas are the serious bug finding stages. A "Release Candidate" does exactly what it says on the tin, it's a candidate for release and is a final safeguard to spot any final bugs.
actually, even if you do not agree with the terms and definitions, you can't do a thing about it... it is general usage in the code development and in the industry that Beta is for fixing development and RC is for bugs roundup... you would have to argue with the base of the internet to make it change...
Sorry to be pedantic but I think it's important in this case... RC's should NOT be the serious bug finding stage!!! Betas are the serious bug finding stages. A "Release Candidate" does exactly what it says on the tin, it's a candidate for release and is a final safeguard to spot any final bugs.
In an ideal world all bugs are fixed after the last beta, and then a RC is released without bugs - that RC then goes Gold/RTM and Bob's your cousin's father. Of course in many cases there'll rightly be several RCs just to ensure that all bugs are indeed caught - but when a RC is released with no bugs (or just a couple of minor ones that can be fixed without having an impact elsewhere), then the code is ready to go Gold/RTM.
I know - I need a slap for being so pedantic, but it's happening more and more where RCs are treated like Betas, and final software is treated like RCs, and I think it's healthy just to stop and think about each part of the design/release cycle of software - to set expectations correctly and to back up programmers/coders when users/owners are expecting too much.
Oh, and happily been using 3.7b3 since its release without any issues - will be upgrading to 3.7b5 this weekend!
To clarify things, by saying serious bug finding stage I meant the RCs concentrate on finding the final bugs and that is their main propose, not adding or changing a lot of things anymore.
And the part about me being your cousin's father, I have apologized for that over and over and sent all the support payments. What else do you want?
i just finished the upgrade, the vb upgrade took me about 10minutes, with prepared the changed templates on my localhost, 5 more minutes to write a simple permission plugin for the thread prefixes, after that 2 more hours to switch my site news system from the forum category, to the thread prefix system. 2K Threads moves, thx god it's over.
I am running version 3.6.8. Is there any way to install this in a different directory but use the same database to make sure it works first? I'm assuming no but wanted to ask.
I am running version 3.6.8. Is there any way to install this in a different directory but use the same database to make sure it works first? I'm assuming no but wanted to ask.
you can make a backup of your site and set that up in a test sub-folder, change the db name and everything.
I am running version 3.6.8. Is there any way to install this in a different directory but use the same database to make sure it works first? I'm assuming no but wanted to ask.
No you can not use the same database (unless you install twice with different table prefix). Installing 3.7 using your production database would upgrade all tables to their 3.7 version, leaving your 3.6.8 installation useless.
Would be good to have a stable full release soon rather than all these BETA's
I do understand that they are needed in order to release such a version, but 5??? we are having more? LOL Surely this could be compacted a little but nevermind, keep up the good work vb team!
hum, actually, as this site is dedicated to development and coding, it is the worst place for the regular public to look at when they are stressed about releases...
if you do not like betas and alphas, do not visit this site... you'll be disapointed all day long
02-15-2008, 01:34 PM
Linear Mode
