Hello! Thank you for the quick feedback! I do take your point. On Чт, 2021-09-09 at 08:52 +0100, Jonathan Wiltshire wrote: > > On Wed, Sep 08, 2021 at 10:49:30PM +0300, Nicholas Guriev wrote: > > A possible test-case is described in the aforementioned bug report. > > It is, but you haven't said what testing you have done for this upload - > that's what I'm really interested in here. In the bug report you say: > > > The patch that should fix the issue is attached. > > which doesn't help to clarify much. I personally did a local build with pbuilder(8), followed the steps and made sure the patched application was not closed abruptly. Those steps describe interaction between two accounts, first one uses most recent version (either desktop or mobile) and second one is logged into the app of version 2.6.1+ds-1. I had no chance to verify that the message would disappear after 30 days, though. A computer should be uptime all these 30 days, or the timer will be reset. Maybe is there something I can add to the original bug report to clarify the issue or explain the patch? I thought it was understandable. But perhaps my eyes are swimming. > This changelog doesn't easily help a user to understand why they want this > update. It doesn't need an essay but briefly describing what this is fixing > would help more them I think. Ok. I should have appended some kind of line like "- Fixes crash on a long-lived message when auto-delete is set".
Attachment:
signature.asc
Description: This is a digitally signed message part