CLAMXAV REVIEW 2015 PATCH
Both of these can be found on /downloads, with 0.104.1 as the main release and 0.103.4 under "Previous Stable Releases."ĬlamAV 0.103.4 is a critical patch release with the following fixes: If you choose to migrate any tickets from Bugzilla to GitHub Issues, please add references in each ticket and close the original Bugzilla ticket(s) to assist our team with the ticket queue maintenance.ĬlamAV 0.103.4 LTS and 0.104.1 patch versions are out now. If you have an open ticket on Bugzilla and would like to help migrate it to GitHub Issues, we would appreciate the help. Effective immediately, the new ticket creation form on will redirect users to the new issue creation page on our primary ClamAV repository on .Įxisting open tickets on Bugzilla will remain open for now, and the Bugzilla server is expected to remain available through 2022 as we complete this transition. With users following guidance in the template, the bug reports are generally easier to triage and respond to intelligently.Īll that being said, we will disable Bugzilla ticket creation so we can focus all new bug reports towards GitHub Issues.
![clamxav review 2015 clamxav review 2015](https://uip.me/wp-content/uploads/2015/02/vir2.jpg)
With the aid of issue templates, the quality of bug reports coming through GitHub Issues has also been of a higher caliber than those coming through Bugzilla. At this point, most of our reports come in through GitHub Issues. Since enabling GitHub Issues at the start of June, we have found that using GitHub Issues has been a very positive experience. While Bugzilla requires users to make an account on our server, enabling GitHub Issues would open up bug reporting to the wider GitHub community that already has an account. Initially, this would supplement our aging Bugzilla server. Our daily routines drew our attention away from GitHub.Īt the same time, we also settled on a plan for how we could test using GitHub Issues for ClamAV bug reports. That made it tougher for us to connect to and work with contributors from the ClamAV community. The public GitHub repository was just a mirror. Before then, our primary Git repository was sequestered to the Cisco corporate network.
![clamxav review 2015 clamxav review 2015](https://uip.me/wp-content/uploads/2015/02/vir1.jpg)
In early 2021, we made a decision to switch to using GitHub directly.