-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new release #269
Comments
I know about it. But I was not able to spend time recently to debug the testsuite failure. and making a release while the testsuite is red is not a good message. |
Is there anything blocking the creation of the 1.4.0 release now? Even with the |
@greg-1-anderson , nothing is blocking us. The change log is ready, so it's up to @stof to create release on GitHub. |
@stof Could you please make a stable release here and in minkphp/Mink? We only have a few short weeks before Drupal 8.8.0-alpha1. The closer we get to that deadline, the more difficult it will be to get the attention of core committers. If you do not have time to make these releases, could you please make @aik099 a maintainer of these repositories? It is good to spread the responsibility of maintenance a bit, and the community could really use a new release here. Thank you very much for your attention. |
The new release was prepared more than a month ago in 3ab9f31. The features in the unstable branch are needed by a lot of people who are using unstable because there hasn't been a stable in three and a half years (1.3.1 on Mar 5, 2016). It seems that all is needed here is the tag / GitHub release, which should only take a few minutes. Could @stof or someone please do that? Please? |
We ran into this again when updating Drupal to 8.8. Any news on creating a new release? Is there anything we can do to help? Or perhaps making a temporary fork only to create a tagged release? |
There have been several requests in #252 to make a new release for MinkSelenium2Driver, but these are probably not very visible since that PR is closed.
So here is a separate issue for it :)
The text was updated successfully, but these errors were encountered: