Skip to content
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

New release ? #99

Open
fengtan opened this issue Jun 28, 2018 · 7 comments
Open

New release ? #99

fengtan opened this issue Jun 28, 2018 · 7 comments

Comments

@fengtan
Copy link

fengtan commented Jun 28, 2018

Hi and thanks for this great plugin.

Any chance you could make a new (possibly beta) release in the near future ? The last release (v0.1.0) was published 3 years ago. Some very interesting features have been committed since then (screenshots !) and I'd love to use them.

@fr33ek
Copy link

fr33ek commented Nov 13, 2018

Same here. Or should we just use master-dev? :(

@donkidd
Copy link
Collaborator

donkidd commented Nov 21, 2018

I'm just using "dev-master" for now.

@ptmkenny
Copy link
Contributor

ptmkenny commented Sep 2, 2020

Related: #110

@RoSk0
Copy link

RoSk0 commented Oct 22, 2021

Can you please tag a new release @PurHur ?

There is couple good additions since the last release , like

Hopefully this will help revive community around this good plugin .

@PurHur
Copy link
Collaborator

PurHur commented Nov 3, 2021

A new release would be good indeed. But i dont see how this will be a "good release".
Currently its very recommended to use dev-master (or further more the current commit hash). With that people understand the implications of how unstable it is.
I rather would add that to the top of the readme.

A sidestory of my dev live:
I use this tool too. But sadly i dont have a pipeline in place now. At the very moment i work on setting up my software stack automatically, and then i would install a huge behat testpipeline, including this package. The hope is that this will be done in 1-2 weeks.

After that i will maintain this package a lot more than now. But i understand how difficult the situation currently is. This package is barely maintained due to many reasons but is used in a lot of testing stuff.

@PurHur PurHur closed this as completed Nov 3, 2021
@PurHur PurHur reopened this Nov 3, 2021
@donkidd
Copy link
Collaborator

donkidd commented Nov 3, 2021 via email

@PurHur
Copy link
Collaborator

PurHur commented Nov 3, 2021

Also noted in #110 we currently cant tag new releases for a composer package. You would still need to use a workaround by hash/branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants