Fedora Release Process


Pre-Requisites

Fedora already has all of the packaging packages in the default repos - no additional configuration is required.

If you are using RHEL/CentOS/similar derivative to do Fedora packaging, you will need to configure the EPEL repos. For example, for EL6:

yum install http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm

Then, install the packager packages:

yum install fedpkg fedora-packager

You will need a FAS account at https://admin.fedoraproject.org/accounts/user/new

git push access - you will need to be a member of the git389 group in FAS

DS = the 389 source code SCM - git clone ssh://git@pagure.io/389-ds-base.git

Fedora = the DS clone location which contains the spec files - (use fedpkg clone 389-ds-base)

DS - checkout the source, add the fixes, set the version, tag it, and archive it

Fedora - Clone it, and update the spec files

DS - Create version specific archive and gather the changes

Fedora - Finish editing the spec file, verify the version, and do the scratch-build

Fedora - Do the official Koji build, and do the release “update”

DS - push the updates and the tag

NOTE: Do not push the tags until you are sure the builds were successful! Once you push a tag, you cannot change it - if you need to make a change to fix a build problem, you will essentially have to repeat all of the steps again, since this will involve a new source version.

NOTE: Do not git push --tags - you may inadvertently push tags you did not intend - push tags specifically by name

Update The Wiki (internal use only)

Last modified on 18 June 2017