- Issue created by @ressa
- Status changed to Fixed
12 months ago 7:19pm 10 December 2023 - 🇫🇷France Dom.
I had to create a whole new branch because of this:
✨ [D7EOL] - Do not allow Drupal 7 branches of projects to be re-supported after Aug 1st FixedThat might be confusing now to users though since due to the release date it will sound like 7.x is still supported which is not the case.
- 🇩🇰Denmark ressa Copenhagen
Thanks for creating a new branch.
Do you know why this happened? If yes, maybe you can share the reason, so that other Drupal 7 module maintainers don't end up in the same situation. Maybe an issue needs to be created, or a comment left in ✨ [D7EOL] - Do not allow Drupal 7 branches of projects to be re-supported after Aug 1st Fixed ?
- 🇫🇷France Dom.
Oh, totally down to my fault.
I received an automatic email from drupal.org with a list of modules of mine that still have releases for deprecated Drupal version.
So... I clean it out. Everything below Drupal 9 (did I thought) since the rest is EOL right ? Well.. not D7 that got extended lately.But because of the ticket issue I mentioned, once a branch for D7 is removed from support list, you cannot undo it anymore (since August 1st apparently ).
This used to be a reversible operation so I did minded too much and so there is no warning message.(Now that I mention it, actually that could be worth addressing on that parent issue that a confirmation message could be added)
- 🇩🇰Denmark ressa Copenhagen
Thanks for clearing that up. And no hard feelings from my side, I am just grateful for being able to use the module :)
And yes, perhaps a comment could be considered in that issue, if there's room for improvement in the process?
Automatically closed - issue fixed for 2 weeks with no activity.