It could be done before a 2.1.4 release, but I agree should that be soon.
For this, I'm more concerned about how it's going to mess up currently
outstanding PRs against 3.1... which I'd like to merge first to minimize
impact.
On Tue, Mar 11, 2025 at 5:19 PM Dave Marion wrote:
> I'm wondering if
I'm wondering if we should implement this plan after 2.1.4 is released
(which is hopefully soon).
On Tue, Mar 11, 2025 at 5:16 PM Daniel Roberts wrote:
> I agree with the proposed steps for the 3.1-deprecations branch.
> If we are dropping the 3.1 branch, when should we change our merge strategy
I agree with the proposed steps for the 3.1-deprecations branch.
If we are dropping the 3.1 branch, when should we change our merge strategy
for 2.1 changes?
There's a couple of on-going efforts that are resolved in preparation for
the 2.1.4 release.
Should we continue to merge them forward via th
