Upstream release

Start with upstream release process.

Commit new version to Fedora git

• Login with your FAS account

  $ kinit username@FEDORAPROJECT.ORG
  

• Upload new tarball to lookaside cache

  $ git clean -fdx
  $ fedpkg new-sources bind-dyndb-ldap-??.?.tar.bz2{,.asc}
  

• Edit RPM SPEC file

  • Update Version

  • Update Release

  • Add note to %changelog

    • Date format: LC_TIME=C date '+%a %b %d %Y'

    • Header line template:

      $ echo "* $(LC_TIME=C date '+%a %b %d %Y') $(git config --get user.name) <$(git config --get user.email)> - "
      

      • Do not forget to add version number to the end, e.g.:
      • * Fri Jul 26 2013 Petr Spacek <pspacek@redhat.com> - 2.3-4

• Test new SPEC file

  $ rpmlint bind-dyndb-ldap.spec
  $ fedpkg local # produce bind-dyndb-ldap-??.?-?.fc??.src.rpm
  $ sudo dnf install $(uname -m)/bind-dyndb-ldap-*.rpm # install new RPMs
  

  • Run BIND and do some sanity checks

• Push changes to Fedora git

  $ git add bind-dyndb-ldap.spec
  $ git diff --staged
  $ git diff  # should be empty
  $ git commit -S
  $ git push -vn
  $ git log   # commit range
  $ git push -v
  

• Always merge changes to Fedora Rawhide

  $ fedpkg switch-branch master
  $ git merge f??
  $ rpmlint bind-dyndb-ldap.spec
  $ git push -vn
  $ git log   # commit range
  $ git push -v
  

Build new package

• Start with Rawhide

  $ fedpkg switch-branch master
  $ fedpkg build # start build process for current branch
  

• And do not forget to released Fedoras :-)

  $ fedpkg switch-branch f??  # select Fedora version for build
  $ fedpkg build # start build process for current branch
  

Buildoverride hints

• Add particular build as an override in Bodhi
• Wait until build override is ready: koji wait-repo f18-build --build=bind-9.9.2-9.P1.fc18
• Run bind-dyndb-ldap build

Push package to updates-testing

• fedpkg update creates an update request within Bodhi

Links

• Using Fedora Git
• Package update HOWTO