Taking this out of the previous discussion because it probably wasn't pulling people in to check on it with that topic, what would it take to get a change in the way updates are put out? How many &votes&? I know a lot of hosts as well as resellers that are a little tired of the updates coming through and having their servers used as a beta environment. I realize that people can always switch control panels, but why can't we just improve the way this one is put out? It would only improve cpanel to have better beta testing.
We need a way to update to something where the features have all been tested (not only by darkorb as that hasn't been working out) and proved stable. Granted that bugs may pop up still, but at least it shouldn't be as bad as just releasing a full blown test on production servers. It would be great to be able to do an update where all the features there have been tested for a good couple of weeks, instead of waiting for one problem to be fixed, only to download it and find one problem's been fixed, but two more new features got put in with bugs.
Why not set certain features to be done and tested (letting us know these plans ahead of time via a mailing list or something) for a certain release and then letting people download and use that release for a week. Fix any further bugs (this is AFTER 2 or so weeks of testing beforehand) and then begin work on the next release. You don't have to be coming out with new features once a week. Give a good long gap inbetween features and get some breathes in.
Help us help you. There are some of us here more than willing to go through with such a beta server idea, it just needs to be implimented. This is not meant to be a flame or anything of that nature. Nick's been extremely helpful with everything, I and others just feel there needs to be a little change in the structure of releases.
We need a way to update to something where the features have all been tested (not only by darkorb as that hasn't been working out) and proved stable. Granted that bugs may pop up still, but at least it shouldn't be as bad as just releasing a full blown test on production servers. It would be great to be able to do an update where all the features there have been tested for a good couple of weeks, instead of waiting for one problem to be fixed, only to download it and find one problem's been fixed, but two more new features got put in with bugs.
Why not set certain features to be done and tested (letting us know these plans ahead of time via a mailing list or something) for a certain release and then letting people download and use that release for a week. Fix any further bugs (this is AFTER 2 or so weeks of testing beforehand) and then begin work on the next release. You don't have to be coming out with new features once a week. Give a good long gap inbetween features and get some breathes in.
Help us help you. There are some of us here more than willing to go through with such a beta server idea, it just needs to be implimented. This is not meant to be a flame or anything of that nature. Nick's been extremely helpful with everything, I and others just feel there needs to be a little change in the structure of releases.