Author Topic: NEW VERSION: 2016.11.2.2262  (Read 45161 times)

0 Members and 1 Guest are viewing this topic.

Offline Skakara

  • Full Member
  • ***
  • Posts: 198
Re: NEW VERSION: 2016.11.2.2262
« Reply #30 on: April 28, 2016, 01:34:34 PM »
Yes we did this in the past, but we changed it last year, because it was causing troubles. To ensure the best quality we always want to have the "release" binaries in beta channel first for few days to see if it's stable, before we push it for general use.

Yes of course we have our internal QA, automated/manual testing, but we are never able to simulate all scenarios, machine configurations etc that exist in the real world. Here is the great help of the beta community.

I hope this makes sense..

Here's yet another example of how engineer-mind works. You don't seem to understand the end user side at all. Users only see that there's 2 releases with same version number, they don't care nor possibly understand how it works internally in avast labs. Like forum veteran DavidR said, there's constant confusion in forum about the versions because of what you do currently.

Offline -Malware-

  • Jr. Member
  • **
  • Posts: 53
Re: NEW VERSION: 2016.11.2.2262
« Reply #31 on: April 28, 2016, 02:41:33 PM »
Boring update :(
« Last Edit: April 30, 2016, 08:55:35 AM by Captain Awesome »

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 83537
  • No support PMs thanks
Re: NEW VERSION: 2016.11.2.2262
« Reply #32 on: April 28, 2016, 02:57:33 PM »
Yes we did this in the past, but we changed it last year, because it was causing troubles. To ensure the best quality we always want to have the "release" binaries in beta channel first for few days to see if it's stable, before we push it for general use.

Yes of course we have our internal QA, automated/manual testing, but we are never able to simulate all scenarios, machine configurations etc that exist in the real world. Here is the great help of the beta community.

I hope this makes sense..

Considering the version number hasn't changed, what is the point of having the "release" binaries in beta channel first for few days to see if it's stable, if nothing has changed. When you could keep it in beta for a few more days to confirm stability.

If something had changed then I could see the point of it staying in or being released to the beta channel, but for the same reason (if something had changed) surely the program version should also see an increment .2263, etc.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 20.6.2420 (build 20.6.5495.561) UI-1.0.541/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 66030
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: NEW VERSION: 2016.11.2.2262
« Reply #33 on: April 28, 2016, 03:05:43 PM »
I agree, that it would be easier to follow (for average users) if build# for beta and final differs.
Win 8.1 [x64] - Avast PremSec 20.7.2421.B#1 [UI.544] - CC 5.70 - EEK - FF ESR 68.11 [NS/AOS/uBO/PB] - TB 68.11 - SB/CP/SL/DU.BC
Deutschsprachiger Bereich -> Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1787
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
Re: NEW VERSION: 2016.11.2.2262
« Reply #34 on: April 28, 2016, 03:23:52 PM »
this new update is bad, broken and should not ever reach end user ...

or the installer or it's content is messed
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Secondmineboy

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3651
Re: NEW VERSION: 2016.11.2.2262
« Reply #35 on: April 28, 2016, 03:38:28 PM »
this new update is bad, broken and should not ever reach end user ...

or the installer or it's content is messed

Not a single issue upgrading from the UI on Windows 10s latest stable Build :)
Windows 10 1909, 4 GB DDR3 RAM, 500 GB 5400 RPM HDD, 1366 by 768 LCD Screen, Intel Core i3 5010U Dual Core, Intel HD Graphics 5500
HUAWEI P30 Pro. Android 10

Offline petr.chytil

  • Quality Assurance Director
  • Moderator
  • Full Member
  • *
  • Posts: 124
Re: NEW VERSION: 2016.11.2.2262
« Reply #36 on: April 28, 2016, 05:29:30 PM »
this new update is bad, broken and should not ever reach end user ...

or the installer or it's content is messed
Dwarden,
please, could you be more specific? Do you have an issue with the release installer? Online or offline version? Which edition, OS?
Thanks!

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1787
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
Re: NEW VERSION: 2016.11.2.2262
« Reply #37 on: April 28, 2016, 05:30:28 PM »
this new update is bad, broken and should not ever reach end user ...

or the installer or it's content is messed
Dwarden,
please, could you be more specific? Do you have an issue with the release installer? Online or offline version? Which edition, OS?
Thanks!

the both updater and installers failed, I will send you PM
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Chippers

  • Newbie
  • *
  • Posts: 3
Re: NEW VERSION: 2016.11.2.2262
« Reply #38 on: April 29, 2016, 12:44:41 AM »
I reported yesterday that after updating Avast I could not load Chrome, although I had tried re-booting several times.
Well today I can load Chrome. Also, interestingly, MS-Mail would initially only load in safe-mode.
I noticed also that the Avast update changed many of my Chrome settings and added in plug-ins that I had previously deleted so I suggest users check their own settings..

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 43878
  • 60 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: NEW VERSION: 2016.11.2.2262
« Reply #39 on: April 29, 2016, 12:56:49 AM »
I reported yesterday that after updating Avast I could not load Chrome, although I had tried re-booting several times.
Well today I can load Chrome. Also, interestingly, MS-Mail would initially only load in safe-mode.
I noticed also that the Avast update changed many of my Chrome settings and added in plug-ins that I had previously deleted so I suggest users check their own settings..
What settings in Chrome were changed ???
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v1909 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.3.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline iamond98

  • Newbie
  • *
  • Posts: 2
Re: NEW VERSION: 2016.11.2.2262
« Reply #40 on: April 29, 2016, 03:24:06 AM »
unfortunately,when I launch avast IS,it freezes my computer.
windows 10,xps 13

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1787
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
Re: NEW VERSION: 2016.11.2.2262
« Reply #41 on: April 29, 2016, 05:34:11 AM »
repeated attempts to use 2262 installer and restarts finally resolved my 'update' issue

sadly the case what went wrong is unknown (no dumps, logs seems ok)

yet I can tell everyone good news, one of major AvastSvc.exe resources leaks is now fixed in 2262  8)
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline gordon451

  • Full Member
  • ***
  • Posts: 165
  • It MUST be beer\\\\food'o'clock SOMEwhere!
Re: NEW VERSION: 2016.11.2.2262
« Reply #42 on: April 29, 2016, 01:08:08 PM »
Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people.

I humbly offer a silly suggestion.  Why not have all beta versions have the build number end with a "b" or "B"?  for example, 2016.11.2.2263B? Which will then change to 2016.11.2.2263RC when nearly ready, which will then become 2016.11.2.2263?  This way, we can follow the progress with no confusion...

Gordon
Gigabyte H61M-USB3-B3 r2.0, I5-2400 3.10GHz, 4GB RAM; W7HPx64 SP1, Lotus SmartSuite 9.8, K-Meleon 76RC, Pale Moon 26.2, Opera 12.17x64, IE11, Clyton email 14.0, Foxit Reader 7.0.6.1126, PaintShop Pro 6.02, Avast! 12.3.2280, SuRun 1.2.1.2, VoodooShield 3.50

Online NON

  • Japanese User
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 4452
  • Whatever will be, will be.
Re: NEW VERSION: 2016.11.2.2262
« Reply #43 on: April 29, 2016, 01:29:21 PM »
Thanks for the update. :)
Main: Win10 Pro 2004 64bit / Core i5-7400 3.0GHz / 16GB RAM / Avast 20 Premier Beta / Comodo Firewall 12
Mobile: Win10 Pro 1903 32bit, Vista SP2 32bit / Core 2 Duo SU9300 1.2GHz / 4GB RAM / Avast 20 Free / Windows Firewall Control

Avast の設定について解説しています。よろしければご覧ください。

Offline -midnight

  • Super Poster
  • ***
  • Posts: 2391
Re: NEW VERSION: 2016.11.2.2262
« Reply #44 on: April 29, 2016, 01:49:11 PM »
Updated with no issues.