| Summary: | Mutt 1.7.1 was released on October 8, 2016 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Don Pellegrino <don> |
| Component: | mutt | Assignee: | Matej Mužila <mmuzila> |
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | databases-maint, don, hhorak |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-07-25 07:06:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Don Pellegrino
2016-11-17 15:37:00 UTC
Is there any specific feature or bug fixed that you would like to see update for? I use the IMAP backend and the release notes indicate "Mutt 1.7.1 was released on October 8, 2016. This is a bug-fix release, fixing an imap segfault along with several other small issues." (http://www.mutt.org/). I would prefer to avoid IMAP segfaults that are avoidable. This would just be preventative maintenance for me and could be given prioritization as appropriate. Thank you for providing that information, we'll consider updating, but I don't expect it will happen any time soon. Fair enough. Thanks. For reference, is there any documentation I could read to better understand the process flow and policies that effect upstream releases flowing into Red Hat updates? (In reply to Don Pellegrino from comment #5) > For reference, is there any documentation I could read to better understand > the process flow and policies that effect upstream releases flowing into Red > Hat updates? (sorry for long delay, this question somehow got from my radar) There are basically two points of view: One is compatibility, that may block something newer from getting into the release (should not be too big problem here, but we didn't look closely yet). Second is an official customer request through https://access.redhat.com/support/, because RHEL updates are customer-driven and only issues with high-enough priority can be addressed. The same site should also provide further info about the process. Since we have no other requests for the rebase, it is not likely that mutt will be rebased in RHEL-7 timeframe, so I'm closing this for now. If this request has a reasonable business reasoning, please, open a case in the customer portal https://access.redhat.com/support/. |