thunderbird-patches
thunderbird-patches copied to clipboard
Upstream bug 1872789: Calender only searches back one year
https://bugzilla.mozilla.org/show_bug.cgi?id=1872789 regressed here: https://bugzilla.mozilla.org/show_bug.cgi?id=1844408
https://www.reddit.com/r/Betterbird/comments/198p0x4/how_can_i_return_this_important_calendar_feature/
Will become relevant for BB 128.
Thank you for logging! I don't know when you plan to release 128 beta. When should I look back for an update?
BB 128 beta comes in May or June 2024.
OH great! Apologies, but I cant' find downloads for current BB betas, only the stable versions. Could you please provide a link?
Generally there are no betas. We'll do a BB 128 beta in May or June ~~2025~~ 2024.
BB 128 beta comes in May or June 2024.
Oh, was 2024 a typo then?
No, 2025 was the typo. The next ESR 128 comes in June/July 2024 and the beta a month before.
Awesome! Look forward to updating then.
Maybe the TB folks are going to implemente something in https://bugzilla.mozilla.org/show_bug.cgi?id=1855900
Maybe the TB folks are going to implemente something in https://bugzilla.mozilla.org/show_bug.cgi?id=1855900
Thanks! After looking at it, it seems just as old and inactive as mine. Is there a reason you believe this one will lead to an implementation from them?
We'll see, if not, we'll do something.
It's a month before the BB 128 ESR. Is there an update on either your implementation or TB's?
Thanks for the reminder. As expected, the TB folks haven't done anything. We'll fix it for 128.
It's a month before the BB 128 ESR.
Well, the official release date is the 9th of July 2024. I doubt that it will be released then, since due to a broken backend, 128 is unusable:
Folder corruption since version 122: https://bugzilla.mozilla.org/show_bug.cgi?id=1890230 Folder compact broken since version 122: https://bugzilla.mozilla.org/show_bug.cgi?id=1878541 POP message corruption since version 122: https://bugzilla.mozilla.org/show_bug.cgi?id=1888790 Also, they rewrote folder compact (https://bugzilla.mozilla.org/show_bug.cgi?id=1890448) so it doesn't work now: https://bugzilla.mozilla.org/show_bug.cgi?id=1900172.
Our best estimate is that 128.3 in October may be usable.
Okay, since October is still quite awhile away, do you think there is still a likelihood that despite the other bugs, TB might also fix the calendar issue by then?
(Edited to fix formatting)
Unlikely.
Okay, thank you for taking this on then!
(Edited to fix formatting)
Looks like the TB folks are fixing this in bug https://bugzilla.mozilla.org/show_bug.cgi?id=1855900 now.
Thanks for updating! To me, it just looks like someone keeps starting a repeat bug every few months. I can't see anyone saying they will actually fix it. But I replied to promote it since my bug was marked as a dupe.
Don't worry, you will get something workable. The new bug has a fix attached which is waiting for review. If that's not enough, we'll improve it.
Okay, I'm not understanding the programming lingo on there. When should I check in? Or will you update like before?
If you are Sanded7279 on BMO, you will get updates on the bug. If two years back is not enough, we can increase that value. Surely 100 years ago you wouldn't have had any appointments (unless you're the Flying Dutchman).
I have important dates for memories including medical records that go back 40+ years that I've entered into my calendars. I need the whole history to be accessible as it was before the feature was removed.
Okay, please keep me updated if you find a significant development or workaround.
(Edited to fix formatting) - When you answer via e-mail, please make sure only to send the relevant text, I've had to edit three replies so far.
If the TB folks stick with the 2-year limit, we'll likely increase to 100 years. Let's assume that no one gets older than 110 years and that in the first 10 years they don't book any appointements.
If you have such important calendar content, please make sure it's duly exported and backed up.
UPDATE: Looking at the code the TB folks are proposing, it looks like the search would start with "date 0", so everything after 1970 should be covered. Most computing is like that.
Thank you, I really appreciate you.
Good Lord, https://bugzilla.mozilla.org/show_bug.cgi?id=1855900 stalled 😢
We looked at the fix in the bug and it looks good to us, We'll ship it in the next 128 build.
Note that TB's technical director got it wrong, see: https://phabricator.services.mozilla.com/D212771
Quote: This is a feature that has been broken since 115 and we didn't get many duplicates.
That's wrong. This feature has worked from day one until it was removed here https://bugzilla.mozilla.org/show_bug.cgi?id=1844408 in version 118. So it clearly worked in 115.
Hi! Thanks for update. I'm confused.
Is there simultaneous development by both apps to fix this bug for
version 128?
And TB: https://phabricator.services.mozilla.com/D212771:
"This is a
feature that has been broken since 115 and we didn't get many
duplicates.
We're gonna start a complete calendar rebuild around September
so it's not worth trying quickly fix a niche feature that was
removed due to multiple issues.
Let's defer this to after ESR."
- Thanks
EDITED with quoted part removed.
Yes. One TB developer suggested a solution, two others rejected it with the following arguments:
- WRONG: The feature has been broken already in 115 (like for more than a year) and no on complained.
- BAD ARGUMENT: Calendar will be overhauled in September (2024?).
- Technical nits.
Since the TB folks are usually not sticking to their self-declared aims, maybe users will see the feature restored at some stage in 2025 or 2026, or not at all. Hard to predict.
Ah, okay, they're just quack quack quacking
themselves up and down into the ground over and over, so now
you've decided to actually soar up into the clouds, because you're
tryin' to be the Better bird! Got it!
EDITED and quoted content removed.
Done. Will ship in the next 128 release, likely in 7-10 days.
Muchos Gracias!
EDITED: quoted content removed.