Version: 17.7.2314

[cruiser25]

Today a message in avast UI prompted me to install a new security update, version 17.8.2318. Anyone who knows what´s in this new version update went fine but no release note here yet. Avast antivirus pro. By the way is Antivirus pro no longer for purchase ?
The new version is 17.8.2318 (build 17.8.3705.0) Usually it says a new version is for install not the message security update. Maybe it´s the same or did avast found vulnerabilities that needed a quick fix ? Now I see that this is a beta version. But im am not a member of some beta trying program. I paid for a stable product not for an experimental one. This is not how it should work !

[TheOwner]

Installed on all my PCs version 17.8. Is definitely stable version and work perfectly. Only avast team is too slow writte changelog on forum.

[DavidR]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

[Alikhan]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

I've escalated this on Slack but it is now late evening there ..

[Alikhan]

I have had a reply on Slack. MartinZ will be releasing the 17.8 changelog soon.

[bob3160]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

Do you feel like your repeating yourself

[abruptum]

Avast Free 17.8.2318 Build 17.8.3705.0

  http://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe

[MartinZ]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

The release process isn't happening in one second. Usually the whole process takes more than one hour and it doesn't appear on all servers at the same time. So for some time someone might be getting old and someone new version...

So there are 2 approaches:
1. post the release notes when the release is in process....then someone will complain that the links still point to old version
2. post the release notes with some delay after the release......then someone will complain where the heck are the release notes ;-)

which one you prefer?

[bob3160]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

The release process isn't happening in one second. Usually the whole process takes more than one hour and it doesn't appear on all servers at the same time. So for some time someone might be getting old and someone new version...

So there are 2 approaches:
1. post the release notes when the release is in process....then someone will complain that the links still point to old version
2. post the release notes with some delay after the release......then someone will complain where the heck are the release notes ;-)

which one you prefer?

I would certainly like a different identification system so one doesn't look like a fool when they tell you they are getting a Full release that's the same as the current beta. Especially when there isn't yet any indication of a new full release.
 

[YLAP]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

The release process isn't happening in one second. Usually the whole process takes more than one hour and it doesn't appear on all servers at the same time. So for some time someone might be getting old and someone new version...

So there are 2 approaches:
1. post the release notes when the release is in process....then someone will complain that the links still point to old version
2. post the release notes with some delay after the release......then someone will complain where the heck are the release notes ;-)

which one you prefer?

Changelog without a links - they can be added later via modify option. Message may be something like "The updated version of Avast starts to roll out gradually with the following changes".

[bruce_b]

Doing the update now. The full offline installer took a very long time to download. Usually get it in about 2 - 3 mins total.

[bob3160]

Doing the update now. The full offline installer took a very long time to download. Usually get it in about 2 - 3 mins total.

You aren't the only one doing a download.

[bruce_b]

Yes, I know, but it is usually much faster.

[DavidR]

This should never be released until there is some sort of notification/change log, in the Forum, Avast Blog or other medium.

Confusion would also be greatly reduced if Avast would stop using the same bloody BETA version number for a regular release.

The release process isn't happening in one second. Usually the whole process takes more than one hour and it doesn't appear on all servers at the same time. So for some time someone might be getting old and someone new version...

So there are 2 approaches:
1. post the release notes when the release is in process....then someone will complain that the links still point to old version
2. post the release notes with some delay after the release......then someone will complain where the heck are the release notes ;-)

which one you prefer?

My preference would be 1:
I think that the changelog could appear before the update is actually released.  There would be nothing to add a comment in the changelog that it is released into the regular program update cycle and users may not see it right away on their systems. 

That way those that have a query and visit the forums for clarification, would at least see that a new program update has been released.  But I'm still banging my head against that brick wall (and my head hurts) of releasing the regular program update stream with the same version as the last beta build.

[midnight]

Didn't take very long for me to download.