Facets 3.0.0-beta2 release?

We'll only tag a new release once we get to a more stable situation, this is still undergoing big changes as it is.

@borisson_ after we get a few more tickets merged wonder if we can do a beta2 release. Dev and beta1 are pretty far apart now could be good to close the gap.

beta1 & dev has a huge gap. If we can release beta2 it would be constructive.

I have created the patch of beta1 & dev diff so that we can use this patch to utilize the latest features and patches till the new beta release.

I've added @balbeeryadav's patch to my composer.json file like this:

        "enable-patching": true,
        "patches": {
	    "drupal/facets": {
                "Facets 3.0.0-beta2 release?": "https://www.drupal.org/files/issues/2024-06-01/beta-dev-diff-3394709-6.patch"
            }
	}

But we need to commit all RTBC issues to the dev branch and then merge everything with the Beta2 release as well.

Would be really good to have a beta2 to use instead of dev. Totally agree with the others here.

We'll only tag a new release once we get to a more stable situation, this is still undergoing big changes as it is.

The earliest I see this happening is at drupalcon barcelona.

Is that a hard set date for beta2? Since it’s been about 1.5 years since beta1

We will also need drupal 11 compatibility. 📌 Automated Drupal 11 compatibility fixes for facets Active

According to statistics we have 4,157 sites using the 3.0.x branch.

I mean it can still remain a beta as before, but those sites should not be left behind.

Yes D11 should definitely be included but probably now is that beta1 is pretty different from the current 3.0.x branch that if you're on beta1 that beta2 will break your site.

Not blaming anyone but this is kinda an important module

So would like to formally request permission to fork the 3.0.x branch of facets into a new module space. facet_views or something.
Could move over any 3.0.x that you wanted.

Have you tried messaging the maintainers about promoting new co maintainer(s)?

I guess that would be preferable instead of a fork.

Automatically closed - issue fixed for 2 weeks with no activity.