Requesting a stable release

I know this was filed for the D8 branch, but it's also served as a reminder that we might want to create a stable release on the D7 branch too.

There's probably more work that can be done on the D7 version, but what's there is quite stable and would make an acceptable full release IMHO.

So, I intend to create a full release from the D7 branch fairly soon unless anyone objects.

As for the D8 branch, I'll leave it up to manarth as he's been doing pretty much all the work on that.

Drew: +1 for a stable release of the D7 branch…it's been going for years, and has had significant usage. Unless anyone else chimes in with an issue, I believe it's good to go.

For the D8 version, although it does have some takeup, it has less than 200 users. However, I've only really made use of it in "Unix Socket" mode.

Unfortunately, whilst looking through the code today, I've discovered that TCP/IP mode does not work, and allows infected files to be uploaded. This is a critical issue that will prevent a 1.0 release.

The D8 version needs more work, and more testing (ideally I'd like some automated tests). I'm also hoping to refactor it as a service, which, although that is a separate issue, it would be good practice for working with D8, and useful to introduce prior to an 8.x-1.0 release.

There is now a 7.x-1.x stable release (complete with the shield icon on the project page).

I've put some time in over the last few days, thinking about what's appropriate for an 8.x-1.0 full release, and fixed some of the important issues:

- Critical fix for issue #2806843: 8.x allows infected files to be uploaded in TCP/IP mode.
- 8.x-1.x has been significantly refactored to work as a Drupal service.

These have been committed to 8.x-1.x-dev.

I think it's appropriate that the upgrade-path issue #2803313: Provide an upgrade path from D7 to D8. is also addressed before releasing it as a full 1.0, so I've labelled that as a release blocker. That issue is next on my list.

Once that issue is fixed, I'll create another alpha release for 8.x-1.x.

To give a suggested roadmap/timeline towards a full 8.x release, I'd like to provide a reasonable amount of time in alpha and beta, to allow issues to be raised.

- If that alpha release (or a further alpha release) lasts 4 weeks without a critical issue, I'll release a beta.
- If a beta lasts 4 weeks without a critical issue, I'll then create a full 8.x-1.0 release.

In the interim, I think it's important that we recognise that 8.x-1.x doesn't have as much test coverage or usage as we'd like, and any testing/feedback would be greatly appreciated. Please go forth and test :-)

The D7 to D8 upgrade path has been committed, and I've created a new release: 8.x-1.0-alpha4. Unless any new critical issues are discovered, that will progress to a beta release in 4 weeks time, and a full 8.x-1.0 release 4 weeks after that.

Complete: ClamAV 8.x-1.0 has been released.