Re: [clamav-users] ClamAV® blog: Changes to ClamAV end-of-life policy and a new Long Term Support policy

[Paul Kosinski via clamav-users]

LTS is great! Earlier this year it seemed like I was spending 1 day per week 
trying to keep up with ClamAV updates, lockouts etc. Now I have time to do more 
forward looking software work.


On Fri, 3 Sep 2021 15:52:10 +
"Joel Esler \(jesler\) via clamav-users"  wrote:

> > 
> > https://blog.clamav.net/2021/09/changes-to-clamav-end-of-life-policy.html 
> > 
> > 
> > Changes to ClamAV end-of-life policy and a new Long Term Support policy
> > 
> > Today, we're announcing changes to the ClamAV End-of-Life (EOL) policy to 
> > include a new Long Term Support program.
> > 
> >  <>These are the main points of the updated EOL policy:
> > 
> > Long Term Support (LTS) Feature Releases
> > 
> > ClamAV 0.103 is the first Long Term Support (LTS) feature release.
> > 
> > LTS feature releases will be supported for at least three years from the 
> > initial publication date of that LTS feature version. In other words, 
> > support for the LTS release "X.Y" starts when version "X.Y.0" is published 
> > and ends three years after.
> > 
> > Each LTS feature release will be supported with critical patch versions and 
> > access to download signatures for the duration of the three-year support 
> > period.
> > 
> > A new LTS feature release will be identified approximately every two years.
> > 
> > Users must stay up-to-date with the latest patch versions for continued 
> > support. As of Aug. 28, that means version 0.103.3.
> > 
> > Regular (non-LTS) Feature Releases
> > 
> > Non-LTS feature releases will be supported with critical patch versions for 
> > at least four months from the initial publication date of the next feature 
> > release or until the feature release after that is published.
> > 
> > Non-LTS feature releases will be allowed access to download signatures 
> > until at least four months after the feature release after that is 
> > published.
> > 
> > If the end-of-life for a version has to change due to a compatibility 
> > problem, that prohibits the use of new detection technology or affects the 
> > stability of ClamAV infrastructure, we will announce the end of life for 
> > those versions four months before they become unsupported.
> > 
> > You can find full details for the updated End-of-Life policy, including a 
> > version-support matrix and definitions for the policy terminology in the 
> > EOL policy page in our online documentation 
> > .  

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

[clamav-users] ClamAV® blog: Changes to ClamAV end-of-life policy and a new Long Term Support policy

[Joel Esler (jesler) via clamav-users]

> 
> https://blog.clamav.net/2021/09/changes-to-clamav-end-of-life-policy.html 
> 
> 
> Changes to ClamAV end-of-life policy and a new Long Term Support policy
> 
> Today, we're announcing changes to the ClamAV End-of-Life (EOL) policy to 
> include a new Long Term Support program.
> 
>  <>These are the main points of the updated EOL policy:
> 
> Long Term Support (LTS) Feature Releases
> 
> ClamAV 0.103 is the first Long Term Support (LTS) feature release.
> 
> LTS feature releases will be supported for at least three years from the 
> initial publication date of that LTS feature version. In other words, support 
> for the LTS release "X.Y" starts when version "X.Y.0" is published and ends 
> three years after.
> 
> Each LTS feature release will be supported with critical patch versions and 
> access to download signatures for the duration of the three-year support 
> period.
> 
> A new LTS feature release will be identified approximately every two years.
> 
> Users must stay up-to-date with the latest patch versions for continued 
> support. As of Aug. 28, that means version 0.103.3.
> 
> Regular (non-LTS) Feature Releases
> 
> Non-LTS feature releases will be supported with critical patch versions for 
> at least four months from the initial publication date of the next feature 
> release or until the feature release after that is published.
> 
> Non-LTS feature releases will be allowed access to download signatures until 
> at least four months after the feature release after that is published.
> 
> If the end-of-life for a version has to change due to a compatibility 
> problem, that prohibits the use of new detection technology or affects the 
> stability of ClamAV infrastructure, we will announce the end of life for 
> those versions four months before they become unsupported.
> 
> You can find full details for the updated End-of-Life policy, including a 
> version-support matrix and definitions for the policy terminology in the EOL 
> policy page in our online documentation 
> .


smime.p7s
Description: S/MIME cryptographic signature

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

[clamav-users] ClamAV® blog: ClamAV 0.104.0 released

[Joel Esler (jesler) via clamav-users]

> 
> https://blog.clamav.net/2021/09/clamav-01040-released.html 
> 
> 
> ClamAV 0.104.0 released
> 
> ClamAV 0.104.0 is available as an official release as of today.
> 
> We are also announcing a new Long Term Support (LTS) program today in an 
> update to our End-of-Life (EOL) policy. The LTS will start retroactively with 
> ClamAV 0.103, the previous feature release. This new LTS policy extends the 
> life of 0.103 up through September 2023 and will facilitate the production of 
> more frequent feature releases while enabling users to rely on a supported 
> version for years to come if they cannot keep pace with the feature release 
> cadence. For full details about the Long Term Support program, you can see 
> the LTS announcement blog post 
>  
> and review the LTS policy in our online documentation 
> .
> 
> We're also introducing new install packages to make it easier for folks to 
> upgrade without having to build ClamAV from source and without having to wait 
> for a community volunteer to package the latest release. You can find the new 
> install packages on the ClamAV.net Downloads Page 
> .
> 
>  <>Today you can find:
> 
> x86_64 and i686 RPM packages compatible with RPM-based Linux distributions 
> running glibc version 2.17 or newer.
> x86_64 and i686 DEB packages compatible with Debian-based Linux distributions 
> running glibc version 2.23 or newer.
> An x86_64/ARM64 macOS installer package is compatible with Intel and Apple M1 
> systems.
> x64 and win32 Windows packages are compatible with Windows 7 and newer.
> In the future, we hope to supplement these with ARM64 Linux DEB and RPM 
> packages and an x86_64 FreeBSD package.
> 
> Please note that you may find installations in this release require more 
> manual configuration than when using a preconfigured package provided by a 
> Linux or Unix distribution. See our installation instructions on clamav.net 
>  for more information.
> 
> ClamAV 0.104.0 includes the following improvements and changes.
> 
> 
> 
> New Requirements
> 
> As of ClamAV 0.104, CMake is required to build ClamAV.
> 
> We have added comprehensive build instructions for using CMake to the new 
> INSTALL.md 
> 
>  file. The online documentation will also be updated to include CMake build 
> instructions.
> 
> The Autotools and the Visual Studio build systems have been removed.
> 
> 
> Major changes
> 
> The built-in LLVM for the bytecode runtime has been removed.
> 
> The bytecode interpreter is the default runtime for bytecode signatures just 
> as it was in ClamAV 0.103.
> 
> We hoped to add support for newer versions of LLVM, but ran out of time. If 
> you're building ClamAV from source and you wish to use LLVM instead of the 
> bytecode interpreter, you will need to supply the development libraries for 
> LLVM version 3.6.2. See the "bytecode runtime" section in INSTALL.md 
> 
>  to learn more.
> 
> There are now official ClamAV images on Docker Hub 
> .
> 
> Docker Hub ClamAV tags:
> 
> clamav/clamav:: A release preloaded with signature databases.
> 
> Using this container will save the ClamAV project some bandwidth. Use this if 
> you will keep the image around so that you don't download the entire database 
> set every time you start a new container. Updating with FreshClam from the 
> existing databases set does not use much data.
> 
> clamav/clamav:_base: A release with no signature databases.
> 
> Use this container only if you mount a volume in your container under 
> /var/lib/clamav to persist your signature database databases. This method is 
> the best option because it will reduce data costs for ClamAV and for the 
> Docker registry, but it does require advanced familiarity with Linux and 
> Docker.
> 
> Caution: Using this image without mounting an existing database directory 
> will cause FreshClam to download the entire database set each time you start 
> a new container.
> 
> You can use the unstable version (i.e. clamav/clamav:unstable or 
> clamav/clamav:unstable_base) to try the latest from our development branch.
> 
> Please, be kind when using 'free' bandwidth, both for the virus databases but 
> also the Docker registry. Try not to download the entire database set or the 
> larger ClamAV database images on a regular basis.
> 
> For more details, see the ClamAV Docker documentation 
> .
> 
> Special thanks to Olliver Schinagl for his excellent work creating ClamAV's 
> new Docker