With the caveat of - we’re not deeply considering coding and backporting considerations, We discussed in the DaWGs meeting today and in general are liking the direction of the E) proposal above. To be sure we are understing this, we think it means:
- Feature works full in core 2.20 and above. Any user with that version and a collection with the new fragment time is in happy land.
- For any older versions of core (TBD how far back) - a collection with this new fragment will show some kind of ‘helpful warning’ about missing return value info only visible for core 2.20 and above.
…and we did do a bit of ‘squinting/ignoring’ on the backport of that warning - considering it a bugfix is a bit of a ..squint/ignore, and the more ‘purist’ approach is D - it only exists in 2.20, and we’d probably have to remember in 18 months to socialize this new fragment at the point when most collection maintainers would actually consider implementing it.