Author Topic: BUILD 7.0.1407 need to be removed  (Read 3158 times)

0 Members and 1 Guest are viewing this topic.

BODUL

  • Guest
BUILD 7.0.1407 need to be removed
« on: March 06, 2012, 09:03:29 PM »
Hi...

Just wondering what for build 7.0.1407. is still placed on the servers and web as option. This build coused problem to consumers and it still do. So why is still here? If you ask me I get it replaced a long time ago because like this market share is going down and reputation of avast! is falling.
Do it quickly...

« Last Edit: March 07, 2012, 06:56:50 AM by BODUL »

Arizona

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #1 on: March 06, 2012, 09:11:36 PM »
+4

Gargamel360

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #2 on: March 06, 2012, 09:22:44 PM »
+4
Why 4?  ;D



Anyway,  there is a follow-up being beta-tested right now.  As for "do it quickly", well, that might have been what caused part of the update snafu.  So I would say take you time with the follow up, within reason.

Unless you mean take it down altogether and replace it with 6.#####?   I don't think that will happen....rarely is a software update rolled back, only in situations that are unmitigated disasters (this is not that bad), or big security risks.  To pull an update is pretty contrary to the general mindset of software development

BODUL

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #3 on: March 06, 2012, 09:44:44 PM »
Hi...

I have 7.0.1414. AIS on my 3 PC and I had problem with just one PC with instaler (tiny bug).
Also when I was testing beta 7.0.1403.etc.betas I posted advice here on forum to take it easy and to take time before posting new final release what missed by avast team. After all when the final release is placed out with  all the problems it should be replaced with some of the betas (example 7.0.1414.) as final release because 7.0.1414. is much better than 7.0.1407. There is no need for going back to 6.xxxxx. Or if you ask me 7.0.1412 is very good as final release to stop issues and to be option while waiting new better build.   
Also there are people whom don`t use betas. For them I would publish new release.

So Gargamel360 I hope that now my post is better to understand... :) 
« Last Edit: March 06, 2012, 11:26:33 PM by BODUL »

retlaw

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #4 on: March 06, 2012, 10:00:03 PM »
Hi...

Just wondering what for build 7.0.1407. is still placed on the servers and web as option. This build couses problem to consumers and it still do. So why is still here? If you ask me I get it replaced a long time ago because like this market share is going down and reputation of avast! is falling.
Do it quickly...

I don't understand that also why it is still there ?
 :-\

skay_baltimore

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #5 on: March 06, 2012, 10:01:45 PM »
Unless you mean take it down altogether and replace it with 6.#####?   I don't think that will happen....rarely is a software update rolled back, only in situations that are unmitigated disasters (this is not that bad), or big security risks.  To pull an update is pretty contrary to the general mindset of software development
While this might not constitute an unmitigated disaster (certainly not from a pure security point of view), this situation very well might justify a roll back at least until the full working v 7 (not beta) is released. There might be some suggestion added that would direct those interested in the beta version to give it a try. It's a judgment call, obviously. But there appears to have been more damage to avast's reputation following the release of v 7 than at any other time in avast's history. I can only speak from personal experience. I'd been using avast for years, without any problems except for 1 virus update that caused problems, but that was resolved by the next day, and I accepted that as just a mistake that could happen with any software program.

In this instance, I would not have minded at all if Avast had come out early on and directed people to roll back to v 6.xxx. In fact, an Avast distributor did exactly that here on this site. Yet his post was ridiculed, for various and sundry reasons. That really shocked me, and made me re-think my use of Avast A/V to the point of uninstalling it and installing an A/V from another company. You can judge for yourself whether that was an over reaction or not. I'm just telling you how this update/upgrade affected me. And while I'm only one user, I'm not alone. Even 1% of 140,000,000 is still almost 1 1/2 million people. And while I realize that some people are always going to be unhappy about some aspect of a software program, I think that in this instance, the way Avast handled the problem made the problem worse, not better.
« Last Edit: March 06, 2012, 10:07:22 PM by skay_baltimore »

Hermite15

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #6 on: March 06, 2012, 10:02:22 PM »
it's still there as long as it's the official release, ie as long as the 1414 build is not out of beta... the wait shouldn't be long now.

retlaw

  • Guest
Re: BUILD 7.0.1407 need to be removed
« Reply #7 on: March 06, 2012, 10:13:37 PM »
new version update
http://www.avast.com/en-us/release-history

Version 7.0.1418

2012-03-06

    Improved File System Shield speed
    Improved AutoSandbox stability
    Improved AutoSandbox controls
    Improved gadgets
    Compatibility with Win 8 Consumer Preview
    Greater stability of Outlook plugins
    Other security and stability-related improvements


I wait and see for a while  ;)