See https://src.fedoraproject.org/rpms/lmms/blob/master/f/README.fedora. The samples are not included in the Fedora package because for many of them the copyright status is unclear.
See also this discussion several years ago: https://sourceforge.net/p/lmms/mailman/message/21407315/.
Well, Shotwell was updated in F27 (by kalev) to 0.27.0 when F27 was still Rawhide.
Based on that, I think it totally makes sense to update the package to a newer release, even if it is from the unstable branch. Only other option would be to downgrade the package in F27 to 0.26.3.
Btw, as I read the Feedback Guidelines, karma should reflect this question: "Is the update generally functional?", not (dis)agreement with the update per se.
@dsommers Sorry, but I tend to disagree. This is a change in behavior. The Updates Policy mandates that packages must "avoid changing the user experience if at all possible". Changing the meaning of an option (
--proto in that case) is such a change.
This does not work for me: There's a semantic change in
--proto udp meaning IPv4 and IPv6 now. As our company's server can be reached via IPv6, but doesn't offer OpenVPN via IPv6, no connection can be established - and OpenVPN doesn't fall back to IPv4.
Now, I could use
--proto udp4 instead, alas NetworkManager doesn't offer that as far as I can see.