As a hypothetical, I was mainly concerned about backporting a new F21 java
package as a F20 update to make it available to users still on that
version, and whether that would require javadocs. Just in case, I've added
a "%if 0%{fedora} < 21" condition for javadocs, and the appropriate
Obsoletes line when the condition fails (>=20), but that's more to maintain
in the specfile, and it'd be much simpler to just not declare any
subpackaging for javadocs.-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, Aug 20, 2014 at 8:29 AM, Miloslav Trmač <m...@redhat.com> wrote: > Hello, > > Regarding https://fedorahosted.org/fesco/ticket/1263 > > Does this policy change affect updates to older releases still receiving > updates? Or only F21 and later? > > It has been approved as a F21 Change, so it should affect only F≥21. > Technically, the packaging guideline change is somewhat independent from > the Change process; I’d argue that updates to existing F≤20 packages should > not remove functionality, though. > Mirek > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
