I have a problem similar to the one of RELEASE-NOTES.
After great pains (broken merges, unknown dependencies, etc.)
I have pushed f74ed02ef744138a8d2a87322f81023ddc143a5f where
I have marked some methods "@since 1.19" since I really hope
to have this backported to 1.19 and maybe even 1.18.
How should we handle the @since stuff? What if it never
gets merged to the release branch? If not, which one?
Should REL1_18 say @since 1.18.3 and REL1_19 @since 1.19
or should all consitent mention the lowest (although
1.18.4 may be younger than, say 1.19)?
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?
The answer I got on IRC is that it is usually up to the
developer to plan for which release it should go to
in advance; but I can understand that my changes
won't be allowed into, say, REL1_18 for this reason or another
(they are not security fixes, for example).