Comment 24 for bug 1918874
Revision history for this message
| Marco Trevisan (Treviño) (3v1n0) wrote | #24 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
> is likely to be a maintenance problem when backporting fixes to 21.04 between now and January 2022 (when 21.04 reaches EOL)
That is actually the reason why I wanted to carry those patch, but for the other way around: upstream code changed so much on those aspects, that I don't expect ANY fix coming from 3.38 on the input side, while I do expect improvements on the input-thread code, so keeping in sync with upstream on it would allow us to have upstream fixes and support.
> Also, while we spend days and weeks fixing these regressions in the input thread backport to 3.38, that's time we don't get to spend on GNOME 40/41 for Ubuntu 21.10 and 22.04.
Don't agree here, as I personally did few fixes upstream on the input side that I wouldn't probably have done otherwise, so be in sync with upstream allows us to work with such code, addressing both upstream and downstream interests.