Hi Nagendra, I didn't hear of any plan to backport 3.6 If the issue you referenced is a common one you hit we would need to think on backporting the fix for it in the SRU [1] process.
>From the referenced issue it became clear that this only fixes one out of a >class of issues, and the other fixes are mentioned to not be as backportable. Do you have a list of steps to reproduce the issue, so that one could test a potential backport of at least the fixes that soemwhat apply back to Xenial? [1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Changed in: rabbitmq-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729671 Title: rabbitmq-server package of version 3.6.x for trusty/xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1729671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
