-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Upcoming release this week: v2.1.0 #691
Comments
Commits since v2.0.0
|
Hi @knadh thanks for all your hard work. Just to clarify: Is transactional emails coming in 2.1.0? |
Thanks @danilobuerger. Unfortunately, not in 2.1.0, but the version after. |
@knadh Awesome, thanks! I am so excited for transactional emails in listmonk 😅 |
v2.1.0 is released: https://github.com/knadh/listmonk/releases/tag/v2.1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This release has been delayed by a month as I tried to squeeze in a couple of things, mainly a transactional mailing API. listmonk has the core + scaffolding and all the right pieces to have a simple transactional mailing feature. However, handling templates optimally turned out to be trickier than I thought. Will try to work it out in the next release. I shouldn't have delayed a release for just one big experimental feature. Some more discussion on the release process here: #675
The current
master
now has over a hundred commits with a number of small improvements. An RC is live in our production environment at work (which sends out millions of e-mails weekly) and it's under observation. I always do this before every release as a stress test. This big fix 1b163d1 came out of this.There's a nice PR from @mrhydejc #689 which is pending, but that'll only be available in the next release. It's big and needs to be tested thoroughly (and tweaked a little bit).
All that said, v2.1.0 looks good to be released in the coming week, after a few more rounds of testing. So, February 12th.
The text was updated successfully, but these errors were encountered: