112
edits
No edit summary |
No edit summary |
||
Line 31: | Line 31: | ||
Knowing about a regression is important, but is not sufficient. Even known regressions are sometimes being deliberately ignored (or potential fixing gets postponed to "unknown"). For example, since Thunderbird 10 we have no error feedback for many protocol errors on SSL/TLS connections. If there's a problem with a connection to a server, it | Knowing about a regression is important, but is not sufficient. Even known regressions are sometimes being deliberately ignored (or potential fixing gets postponed to "unknown"). For example, since Thunderbird 10 we have no error feedback for many protocol errors on SSL/TLS connections. If there's a problem with a connection to a server, it | ||
simply doesn't work, without user feedback. | simply doesn't work, without user feedback. | ||
Joshua Cranmer | |||
If the goal is to move primarily to community innovation, then I think there ought to be an explicit roadmap that lays out the changes that we agree want to be made for Thunderbird, to give contributors guidance as to what would be most useful to work on? | |||
I also think it would be useful to have some sort of liaison with the people working on the Gaia email app to explore future possibilities of sharing code. |
edits