** NEW AVAST PROGRAM UPDATE RELEASE CANDIDATE 6.0.1119 **

[Hermite15]

1.  Avast needs to start identifying the installer file as a Beta in the file name

yes, because too many people don't read or understand Vlk's posts... although it's crystal clear

2.  Avast needs to start identifying the release as Beta in the GUI.

yes, same reason as above.

3.  The forum needs to set up a Beta thread that users have to opt into in their profile in order to get to the Beta release download links.

there's already a beta thread. We're now talking about pre-release versions of Avast, not betas really.

4

.  Eliminate GUI updates for Betas.

why as said that's needed to test updating abilities of the build, and once you're on the beta channel, you expect beta updates, nothing wrong about that. >>> people who are not on the beta channel, ie people who didn't download and install the first beta manually and purposely have nothing to gear from beta updates: as they won't happen. Having to state something so obvious for the nth time is sort of... okay

5.  Put up a big disclaimer and warning right above the installer links, not a one sentence comment about the release being a Beta release.

yes okay, although Vlk again makes it clear that the build is a pre-release.

[Lisandro]

By the way, I agree with you and Logos on 1 and 2.

[sded]

Why should Avast! be interested in limiting usage of an open beta or RC or prerelease?  The idea is to get it out to as diverse a group of testers as possible before it is released in order to try to cut down the problems of the wider audience of 150M or so people.  And if a few people get it unintentionally and have problems that go into the fixit pile, so many problems less to deal with downstream.  

[EvilDust]

Clean install of this build in Windows 7 x64, all run well but Mozilla Firefox 6.0a1 x64 (Nightly build) no more start (error everytime). Mozilla Firefox 5.0b x86 running well, no errors, but the web app of Avast is incompatible.

 

[igor]

Well, seeing the thread having gone completely off topic, i.e. rendering the beta kinda pointless... maybe we should forget about betas altogether?

[warlock]

Nice, I just changed my connection and because AIS was unable to detect the new network (bug 1) I just manually deleted all network profiles, stopped the firewall, restarted it and this time it detected the new network just fine, but immediately froze. Looking in Process Explorer, I now have two afwServ.exe processes, one at 100% CPU (bug 2).

[Lisandro]

Well, seeing the thread having gone completely off topic, i.e. rendering the beta kinda pointless... maybe we should forget about betas altogether?

No Igor... just the thread is bloatware by its nature... Maybe you have to open the beta forum each time and each user open a thread for his/her problem.

[mattburles]

i have determined that avast is blocking something on my internet connection because every once and awhile i get no internet connection. i know this has to do with avast because when i have avast on i receive this problem and when i turn avast off it goes away 

[g0dsends]

nice beta test copy no issue other than google chrome web rep 

[RB123]

Just downloaded 6.0.1119 So far, everythings fine. But in the past Avast 6.0 versions, I would get a BSOD after one week. Will keep testing.

[yongsua]

has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.

Now that is a very good suggestion imho. Might worth considering there.

To be honest making it too easy for people to use beta or pre-release builds is a bad idea. Even with beta or pre-release versions being notified in the forums there are still people that shouldn't be running beta builds of security software on their systems.

For many they don't understand the potential for problems and that it could have serious repercussions that they simply aren't experienced for. Unless you are using a test-bed system or have a robust backup and recovery strategy (disk imaging software, etc.), then you really shouldn't be running beta builds of security software and that includes avast.

But this is rather off-topic for this topic.

At least many ESET users run pre-release updates without any ill effect, including myself.

They are thoroughly tested before they are release for public consumption.(Off topic)

[Jack 1000]

I am a little confused,

There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum?  Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?

Jack

[Lisandro]

I am a little confused,

There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum?  Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?

Jack

+1

[SpeedyPC]

I am a little confused,

There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum?  Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?

Jack

+1

+2

[Hermite15]

may be try to correct this before releasing the next build:
http://forum.avast.com/index.php?topic=77717.0
(tested with current stable)