Here are the recent changes to the packaging guidelines.
-----
A note was added to the Python guidelines indicating that the python2
stack may go away and that upstreams should be contacted about software
not yet ported to python3.
*
https://fedoraproject.org/wiki/Packaging:Python#Python_Version_Support
*
https://pagure.io/packaging-committee/issue/753
-----
The Python guidelines now more clearly indicate that use of %{__python},
%{python_sitelib} and %{python_sitearch} is forbidden.
*
https://fedoraproject.org/wiki/Packaging:Python#Macros
*
https://pagure.io/packaging-committee/issue/745
-----
Information about the automatic shebang line checking and modification
has been added to both the main guidelines and the Python guidelines.
*
https://fedoraproject.org/wiki/Packaging:Guidelines#Shebang_lines
*
https://fedoraproject.org/wiki/Packaging:Python#Multiple_Python_Runtimes
*
https://pagure.io/packaging-committee/issue/738
-----
The guidelines section relating to architecture support has been updated
to reflect the current state of koji's support of
ExclusiveArch:/ExcludeArch: in noarch packages.
*
https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_Unported_...
*
https://pagure.io/packaging-committee/issue/751
-----
A guideline was added showing how to disable buildroot policy scripts
for your package, if necessary:
*
https://fedoraproject.org/wiki/Packaging:Guidelines#BRP_.28BuildRoot_Poli...
*
https://pagure.io/packaging-committee/issue/749
-----
The Documentation section of the main guidelines was expanded to include
information about reducing build dependencies by building documentation
in a separate source package.
*
https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation
*
https://pagure.io/packaging-committee/issue/715
-----
The AppData guidelines were updated to mention the %_metainfodir macro,
which was added to cut down on the need for %if blocks in cross-distro
specfiles.
*
https://fedoraproject.org/wiki/Packaging:AppData#app-data-validate_usage
*
https://pagure.io/packaging-committee/issue/752
Note that redhat-rpm-config/epel-rpm-macros packages supporting this are
in updates-testing, but buildroot overrides are active so you can use
the macro in Koji builds now.
-----
The section on packaging additional RPM macros has been simplified significantly.
*
https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Addition...
*
https://pagure.io/packaging-committee/issue/601
Note that the epel-rpm-macros package supporting this in EPEL7 is in
updates-testing, but a buildroot override is active so you can use the
macro in Koji builds now.