- Issue created by @generalredneck
- πΊπΈUnited States generalredneck Texas, USA πΊπΈ
I've reached out to both Joachim and miiimooo via their contact forms to make sure that just in case they don't have this issue queue followed to email them of new issues, that they are aware of my request above. I had copies of the emails sent to me as well.
- Status changed to Fixed
over 1 year ago 1:08pm 23 August 2023 - miiimooo Europe
Thanks for offering to help with this. I have added you to the maintainers list
- π¬π§United Kingdom joachim
Thanks for taking care of it @miiimooo, and welcome aboard @generalredneck :)
- πΊπΈUnited States generalredneck Texas, USA πΊπΈ
Awesome,
If there's any particular ways yall would like to collaborate or have any ideas on processes for how releases should be made, I want to be mindful and respect that. In other words I want my responsibilities to be clear so I don't step on toes. If it's ok that I take on full maintainership and yall want to pass the torch, that's cool too. Just as long as it's clear. Feel free to reach out on slack if yall want to talk this over in a synchronous way. - π¬π§United Kingdom joachim
I wrote this for a project a long time ago, which I'm no longer involved in and so it's very low down on my list these days, hence not keeping up to date with core compatibility.
One thing to consider doing would be to change to semver - make a 2.0.x branch that's the same as the current branch and a 2.0.0 that's the same as 8.x-1.1.
Automatically closed - issue fixed for 2 weeks with no activity.