Jump to content

Patchwork (software)

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Xose.vazquez (talk | contribs) at 15:02, 5 July 2019. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Patchwork
Original author(s)Jeremy Kerr
Developer(s)Stephen Finucane
Stable release
2.1.4 / July 5, 2019; 5 years ago (2019-07-05)[1]
Repository
Written inPython, Django
Operating systemCross-platform
Available inEnglish
TypeCode review
LicenseGPL v2[2]
Websitejk.ozlabs.org/projects/patchwork/

Patchwork is a free, web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project. It is intended to make the patch management process easier for both the project's contributors and maintainers.

Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too. The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted.

Currently, Patchwork is being used for a number of open-source projects, mostly subsystems of the Linux kernel. Although Patchwork has been developed with the kernel workflow in mind, the aim is to be flexible enough to suit the majority of community projects.

History

Patchwork was developed by Jeremy Kerr for use with the Linux PPC64 mailing list.[3] The ozlabs.org deployment was later expanded to cover additional projects and functionality.[4][5]

Design

Originally written in Perl,[6] it is now written in Python, using the Django web framework. Recent versions of Patchwork use Bootstrap[7] for the front-end UI.

See also

References

  • Official website
  • patchwork on GitHub
  • Ubuntu Patchwork Handbook
  • Stephen Finucane (2016-01-31). "A New Patchwork: Bringing CI, patch tracking and more to the Mailing List" (PDF). Retrieved 2016-08-22.