Skip to content
Michal Fabik edited this page Aug 26, 2020 · 2 revisions
  1. Update the version to x.y.z where needed (currently a manual process):
    • At the time of writing, these are the only files:
      1. CMakeLists.txt
      2. package/abrt-java-connector.spec
    • x = x + 1; y = 0; z = 0 for major releases (significant changes/new features, backwards compatibility is essentially broken)
    • y = y + 1; z = 0 for minor releases (backwards-compatible changes/features)
    • z = z + 1 for bug-fix releases (no changes besides bug fixes)
  2. Run git push <remote> and git push <remote> <new-version>
  3. Publish a new release for the tag in https://github.com/abrt/abrt-java-connector/releases/new
  4. Packit-as-a-Service should create a PR in dist-git (https://src.fedoraproject.org/rpms/abrt-java-connector) for all active branches, review and merge them
  5. Build packages for Fedora:
    $ packit build --dist-git-branch f31,f32,master (update branch names as needed)
    • If there’s need to build in a side tag, then packit build also accepts --koji-target; pass the tag name you get from e.g. fedpkg request-side-tag --base-tag=f32-build (the base tag will vary for each Fedora version)
  6. Create an update in Bodhi:
    $ packit create-update --dist-git-branch f31,f32,master … (update branch names and pass other arguments as needed, e.g. --update-notes and --update-type)
Clone this wiki locally