Packit 0.4.0 & 0.4.1

It’s been over a month since we released packit “0.3.0”. Here comes packit 0.4.0 (and patch release 0.4.1) and as always they bring a lot of new features and improvements.

You can find a complete list in the changelog.

Read More

Packit 0.3.0

In the previous post we promised to provide a new release every 2 weeks and we are already breaking this promise as it’s been 3 weeks since then. We decided to wait with the release to merge several pull requests related to source-git support.

Now the good news. You can find a complete list of new features and improvements of version 0.3.0 in the changelog.

Read More

About

Packit provides tooling and automation to integrate upstream open source projects into Fedora operating system.

Upstream repository

https://github.com/packit-service/packit

The key principles of packit

  • Reuse existing tools and services where it makes sense: don’t reinvent the wheel.

  • You can consume packit in two forms:

    • Packit tool can run on your laptop and you run commands you want.
    • Packit service reacts to events and performs actions which you defined in your packit.yaml.
  • We don’t break backwards compatibility just like that.

  • Packit has a deprecation policy:

    • We can mark a behaviour as deprecated.
    • Deprecated content can be removed or changed after at least 3 minor releases.
    • Deprecated content is advertised in our changelog, printed in terminal or tracked in your issue tracker.
  • We care about artifacts which Fedora supports: at the moment it’s RPMs, modules and container images.

    • Our initial focus is solely on RPMs.
  • Packit respects Fedora guidelines.

  • We want latest content in Fedora Rawhide, but only if it works (the new content can be built and tests are passing).

  • Any task done by the automation system must be able to be performed by a human when that is required. Packit service must be capable of recovering from such situation.

  • Packit developers must be able to iterate on all parts packit (testing a change, merging a change, deploying to production) at a pace of at least every two weeks. To accomplish this, the release and validation processes are completely automated.

  • Contributions to packit must be possible by any developer, maintainer, tester, or other engineer. Any Fedora developer or tester should be able to reproduce a bot locally on their machine, given appropriate credentials.

Read More

Initial version (0.1.0) of packit is out!

We would like to announce general availability of the initial version of packit, titled ‘0.1.0’.

Since this is our first release, we would like to ask you to be patient if you encounter any issues. We work hard on packit’s usability. If you feel like that packit is doing something weird or if anything is unclear, don’t hesitate and reach out to us by creating a new Github issue.

The initial release contains two commands:

  • packit propose-update — Opens a pull request in dist-git for the latest upstream release of a selected repository.
  • packit watch-releases — Watches events for all the upstream releases and performs propose-update for those who use packit.

Read More