breeze/libunwind
1
0
Fork 0
mirror of https://github.com/libunwind/libunwind.git synced 2026-01-12 00:04:03 +08:00
Code Issues Packages Projects Releases Wiki Activity
Page: Maintainers
Pages
Cross Compiling and Testing Current CI Status Documentation Hacking on libunwind Home Libunwind Improvement Projects Maintainers Releases
Clone
5
Maintainers
Dave Watson edited this page 2023-01-05 11:56:29 -08:00
Table of Contents

Maintainer responsibilities:

  • Review / Respond / Merge Pull requests in a timely manner (hopefully sub 1 week).
  • Comment on issues when appropriate - however it seems issue tracking is currently only ~50% relevant, much of it is support requests without enough info.
  • Keep the contbuild running (currently github Actions). This is the primary means of testing changes, since it's unlikely a maintainer has more than a single machine / arch.
  • Cut a release once per year.

Merging Standards

  • Make sure there are no binary breaking ABI changes, unless going to a new major version.
  • Make sure the overall change makes sense
  • If multiple people are reviewing / commenting, try and build some consensus.
  • Far less important, but review for style / quality.

But mostly, bias for acceptance as long as the change makes sense, since this is a community project.

Releases:

  • Update configure.ac with the new version
  • Cut a new branch, vX.X-stable
  • Tag the new branch
  • Test the release: autoreconf; make distcheck
    • Note that distcheck does a 'packaging' step, and only includes files listed in Makefile.am. If someone is complaining of missing distribution files, it's probably not listed in Makefile.am correctly.
  • Push branches / tag (git push vX.X-stable --tags) to github.
  • Make a new github 'release' and upload the package.
  • Savannah stuff:

Let the rc stew for a couple weeks, then promote to non-RC, or cut a new RC if something comes up. Bump minor versions as issues come up.

Unfinished business / backlog of maintainer tasks.

  • Spin down savannah. Mailing lists are already turned off, but likely we could stop pushing releases and uploading stuff there. I never look at the issue tracker there. The documentation is still useful: https://www.nongnu.org/libunwind/docs.html, not quite sure if that can be migrated to a github page or something instead.
  • The contbuild requires constant maintenance, it looks like x86 (32 bit) is currently failing.
  • Possibly build new debian RPMs ourselves?
  • Clean up the issue tracker, close old issues.
  • Remove old arches, like tilegx, which has already been removed from ubuntu.