Since the release of 7.x-1.1, almost 3 years ago, there has been almost 30 commits to the repo. It would be nice to get a stable release out that includes all of these changes. After reviewing the queue I think that once #2241857 is merged you're good to go with a release.

Comments

dydave’s picture

Status: Active » Fixed

Hi @skwashd,

Thank you very much for your interest for the Reroute Email module and for posting this issue.
I can definitely understand your concerns and I am surely aware it's been ages since the previous version was released and plenty of things have changed in dev....

Personally, I really wanted to get a release out earlier and have kept pushing for that... but most of the time, I felt rather alone having to wait for weeks if not months to get feedback, reviews or testing/reporting on some issues (even from the author), especially the ones with patches.
I have tried bumping issues, calling on specific users who had been active in the issue queue and even asking for help on IRC sometimes... sadly it didn't change much.
The only one to really provide continuous feedback, reviews, testing and be more reactive was @jweowu, for whose help I am extremely grateful and without which module would never have got to this level of improvement.

I could certainly conceive that many other contrib modules would require more attention as being more critical or used by a wider range of users. Not to mention all the work and attention that was expected from contributors for moving Drupal 8's development forward.

Anyhow, thanks to your update at #2241857-9: Revert module weight = 99 and implement reroute_email_module_implements_alter(), with testing and feedback, I was able to commit the last patch blocking a new release and here we are.

Very good news:
I would like to gladly let you know that the new releases have been published:

It actually took me some time to write proper release notes due to the amount of changes that had been done since previous releases.

Moving forward:
Now that we've finally reached a new milestone with a new stable version (which definitely includes substantial improvements), we are able to look at the road ahead. Among some of the work to be expected:

I'm sure more work will be stacking up on top of these, down the road, whether related with documentation, support, tasks, new features or bug fixes.
I will follow-up with the issues listed above that haven't been posted in the issue queue yet and create new tickets.

We need help: Reviewing, testing, reporting, patching, answering support issues, etc...
Your contributions are welcome and highly valued!
Feel free to follow up in the issue queue for any contributions, bug reports, feature requests, questions/support requests or tasks.
Tests, feedback or comments in general are highly appreciated.

For now, I allowed myself to mark this issue as Fixed, but feel free to re-open it, or post a new ticket, at any time if you have any further objections or comments with any of the new releases or their notes (6.x-1.3 and 7.x-1.2 - we would surely be happy to hear your feedback).

Please let me know if you would have any further comments, feedback, questions, issues, objections, suggestions or concerns on this comment or this ticket in general, I would be glad to provide more information or explain in more details.

Special thanks to @jweowu for his great help on the module and getting to these new releases.
Many thanks to everyone for your interest, great help, reviews, testing/reporting, feedback and comments for this module.
Cheers!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.