-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REL: yt 4.0.2 meta issue #3555
Comments
3410 is a bit of a bigger deal than bugfix, isn't it? |
IMHO it's not, but feel free to remove it if you're not confortable with it. The bug it resolved was probably not ever encountered in production anyway. |
|
@matthewturk on second thought I think #3410 is not worth the risk of backporting it manually, so I'm taking it off the list. |
We got to a state where PRs can be back ported immediately after they are merged, which is much easier to manage, so I don't think it's worth maintaining this meta issue anymore. The release isn't ready yet but there is no reason left to keep this open. |
Here's a list of existing pull requests that need back porting for yt's next bug fix release
Other devs, please feel free to edit this list if you find it's missing anything
Yt 4.0.1 was released on July 21, so I'm going to add every user-facing bug fix that was merged since then
candidates for back porting (currently not merged)
Notes:
We can strike an item here as soon has it has a backport PR, even unmerged.
items marked with "⭐" contain answer-store updates. These will likely be harder to back port unless we're cautious to reproduce the order in which they were merged.
It would be a good idea to try to reproduce the merging order for the whole list, though it may be hard to do it exactly.
The text was updated successfully, but these errors were encountered: