Hey,
I fully agree with what Chad said.
> Or, once something "@since 1.20" gets
merged in to REL1_19, I should
modify @since to 1.19 in master and update
> master's RELEASE-NOTES-1.19 as well?
We've never listed documentation fixes like this
in release notes, I
don't see any reason to start now.
There actually is a pretty significant reason to not do this. @since tags
are there so people building on top of the software know from which version
something was definitely available, so they can maintain compatibility as
they like. If you go change @since 1.20 to @since 1.19 because you
backported it at some point, people might still have 1.19 from before the
backport was made. So you'd be breaking the core assumption people can make
about @since which is what makes it useful in the first place. @since 1.19
should mean the code is in ALL 1.19 releases and those after that (unless
it gets removed again ofc).
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--