New Release

[tyndyll]

Hi all,

We are currently working through the PR’s and merging them with a view to putting out a new release in the next few weeks.

I can see there are a number of issues that are open, but if there are any new features you would potentially like to see in this next release can you please flag them in this issue? If possible, please only list an existing issue once, and then if it exists 👍 to indicate your interest. If you are requesting a feature that does not already exist please create a new issue first and then link to it here

Thanks for your patience. It’s highly unlikely we’ll get to everything, but your help will give us a roadmap for the next few releases

This issue will be closed when the next release is delivered

Thanks

[jeroenseegers]

Having mailhog/MailHog-UI#7 implemented would be nice!

[staabm]

getting #124 fixed would be perfect.
we could offer also some compensation in case that would make this happen.

edit: just realized that there is even a open PR which claims to fix that problem:
mailhog/storage#9

[tyndyll]

Any more for any more?

[staabm]

In case #166 isn’t a duplicate of #124 it would be great to also have a fix for it

[peter-evans]

We also have issue #166 and it would be great to have a fix.

[tyndyll]

Thanks all. I'll write up a list of what we're planning to have in the next release and get it here next week

[staabm]

a kind of show stopper issue for us is described in #225 which would be great if it could be fixed, or at least improved somehow.

[cuongtran8]

I don't know if it is too late for that but I got that issue also. And It would be great if it got the fix on 1.1: #197

[webyneter]

Any updates?

[lhall-amphibee]

a kind of show stopper issue for us is described in #225 which would be great if it could be fixed, or at least improved somehow.

This one is really bad, I have a server loading 35mb just for listing the 50 first emails.

[monobook]

@tyndyll ping :)

[tyndyll]

Apologies for the delay - I'll have an update on this on Friday 11/2. Any issues that will be addressed in the next release will be tagged with 1.1. Based on the issues and tasks included, I'll provide an estimated release date also

[tyndyll]

Hi all, everything I'm planning to get into this release can be found at

https://github.com/mailhog/MailHog/issues?q=is%3Aissue+is%3Aopen+label%3A1.1

I appreciate that this doesn't get everything that everyone wants, but it's a step in the right direction and the next release shouldn't be too far behind it

You will notice that there are limited UI related issues included. The UI is something I'm going to have to look into a little deeper, not being as familiar with the Angular side as I'd like to be. Those bugs will be addressed in the following releases.

Also, I am aware that there are bugs in the sub projects. I'll get those transferred to here in coming days to make this the central place to see the most current status of the project

Also, please assume that there is a "help wanted" tag on every issue :)

Aiming for a release around the start of April

[allangood]

Hello @tyndyll, any update when the new version will be ready for test?
I've submitted PR #244 to help with this new release. Hope you have some time to look at it.

Thank you!

[tyndyll]

Am hoping for the next few weeks. Apologies - have had a bit on IRL

[peterdd]

Also small releases with bugfixes are ok too. And describe the project in readme what is the purpose of mailhog. Just referencing another project mailcatcher is not enough.

[ahathaway]

Where are things at for a 1.1 release?

[opensourceame]

It's now a year since 1.1 was mentioned and still no release. Surely not all PRs have to be merged. @tyndyll why not release 1.1 now as it is and allocate unmerged PRs to 1.2?

I'm a big proponent of using Mailhog. However it's becoming increasingly more difficult to persuade my clients to adopt it when they look at the releases page on GitHub and see that there have been no releases since 1.0 which was 2½ years ago!

[webyneter]

Should we be expecting a release any time soon?

[tyndyll]

Yes. I suddenly seem to have found some spare time....

Hope everyone is keeping safe

[rwojsznis]

@tyndyll first of all I hope you're doing alright! do you need any help with the release by chance?

[tyndyll]

I'll close this issue with a view to replacing it with a Github project (https://github.com/mailhog/MailHog/projects/1). If there is anything you think should be considered that is missing please not it here. This is the first attempt with this the bug list may vary for 1.1.

I'll close this on 31st August so please update before then

[dregad]

Seeing that this issue has not yet been closed nearly 2 years after @tyndyll's last post, I was hoping that #282 (fixed in mailhog/MailHog-UI#49) could still be included in the scope of the upcoming 1.1 release (although a 1.0.2 hotfix would be fine as well). Thank you !