-
Notifications
You must be signed in to change notification settings - Fork 280
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
Release Mink 1.7.2 or 1.8 #725
Comments
Just bumping this. We're in the process of releasing Drupal 8.3.0 - the alpha is today. And this is the only dependency that's on a commit hash at the moment. Still a couple of weeks to fix that if a new Mink release was tagged. |
To release #747 it should be nice to have a new release :) |
Drupal 8.5.0-alpha1 is around the corner. @stof could you please tag a new release? |
This is becoming a serious issue. Ping @everzet |
Bumping this thread into 2019. |
|
Over in minkphp/MinkSelenium2Driver#313, there is a discussion about the problems that Drupal is having as a result of using a dev-release, to work around the lack of a stable tag. We have the same problem with this repository: Drupal is still using 1.7.x-dev, and has been since Drupal 8.3.0 was released in 2017. When the 1.7.x branch alias in this repository is changed to 1.8.x, every stable Drupal tag since 8.3.0 will break. We could begin to prepare to repair the looming damage if someone could tag a534fe7 as 1.7.2 or 1.8.0. |
@greg-1-anderson , I agree with 1.7.2. If all tests are green, then we only need to prepare a changelog. |
@aik099: I converted a git log (minus trivial changes) into a rough changelog:
Could make that a PR if you'd like. |
@greg-1-anderson , yes, please send a PR where I'll indicate what parts of change log file should be adjusted. |
1.8.0 is finally released (as well as releases of BrowserKitDriver and Selenium2Driver). |
After #720 it would be cool to get a new Mink release so that we can have a concrete version number in Drupal's composer.json.
Currently https://www.drupal.org/node/2808085 uses a git commit hash which is not ideal and people are hesitant to move forward with it.
Any timeline for releasing the next version?
The text was updated successfully, but these errors were encountered: