W13 Posted March 1, 2007 Posted March 1, 2007 I suggest there be a series of public betas before the next version is released. This will reduce the amount of bug-fix versions later on.
bfarber Posted March 1, 2007 Posted March 1, 2007 We had 2 or 3 public betas and another 2 or 3 RC releases for 2.2. :blink:
UBERHOST.NET Posted March 1, 2007 Posted March 1, 2007 I suggest there be a series of public betas before the next version is released. This will reduce the amount of bug-fix versions later on.The series of public betas was successful in reducing the amount of point fixes, but no matter how many betas you release, and no matter how large the beta participation, the updates will still be be necessary.
C_ind Posted March 2, 2007 Posted March 2, 2007 There were lots of betas, so that's not something that can be improved on, but if you're being cynical about it, then from the customer's point of view you should just treat any new version as a large-scale beta. It usually doesn't hurt to wait a few weeks before installing a new version, unless it's an urgent security patch and that's not been the case for the last three ones. Then you'll learn whether the version seems stable in other people's opinion, and you'll be able to search for fixes for most of the difficulties at the support boards.This goes for all software by the way, not just IPB. (Windows, linux distros, php, you name it).
Dark Phantom Posted March 2, 2007 Posted March 2, 2007 I suggest there be a series of public betas before the next version is released. This will reduce the amount of bug-fix versions later on.If you mean they provide you a access to the Betas for "free", it won't happen, since you only have 31 posts, I can only guess what you mean.
Brian Garcia Posted March 2, 2007 Posted March 2, 2007 Its released to paid customers though and there are enough of them to test for bugs and report them as needed.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.