> Personally, I think the removal of the deprecated code which was marked like > that in 3.x is quite safe to do in 5.x but I have to ask broader audience to > have a consensus. Safe for us, sure. Safe for our users, not so much. No amount of including it in release notes guarantees they'll see it, and to Mick's point:
> Anything that is public (user-facing) and is isolated code having little cost > to it should just be left. Strong +1 to this sentiment. On Thu, Nov 30, 2023, at 10:33 AM, Mick Semb Wever wrote: >> Personally, I think the removal of the deprecated code which was marked like >> that in 3.x is quite safe to do in 5.x but I have to ask broader audience to >> have a consensus. > > > Strawman: > Evaluate the cost and risk to us by having to keep the code. > Weigh that against the effort it takes for users to adjust their prod > systems, and assume they are many orders of magnitude more than us. > > Anything that is public (user-facing) and is isolated code having little cost > to it should just be left. > >> I think that what is "private" might go away in 5.x easily. > > > Yes. > > >
