Time for v69.2.0? #4276
Replies: 3 comments 2 replies
-
Up to you, I'm slowly getting more and more into work that could break something if not cautious. It's also why I've kept runtime changes separate from annotation changes as much as possible. Currently I'm blocked on #4246, which is dependant on #4262 . Btw thank you for all your support on this endeavour! |
Beta Was this translation helpful? Give feedback.
-
I have just released v69.2.0 to consolidate all the changes already merged. Let's see if we have any regressions reported, than we can proceed with further changes. |
Beta Was this translation helpful? Give feedback.
-
Good call. Always good to have frequent releases. I do have some distutils changes that need to be merged, but I'd prefer to release those in a separate release anyway, so happy to see the release made. |
Beta Was this translation helpful? Give feedback.
-
Thanks to the amazing work done by @Avasam recently, the codebase for setuptools has been changing rapidly.
I propose that before merging more refactoring (or any other more serious code change) we consolidate the work that has been done so far in release 69.2.0.
The advantage of splitting the PRs among multiple releases is that, it makes it easier to revert/find bugs if they happen.
Would that be fine for you @jaraco, @Avasam?
If that is OK, we can do it in the next few days (this week is good for me, but the 2 last weeks of March I will not be available to help).
Beta Was this translation helpful? Give feedback.
All reactions