Differences between revisions 3 and 4
Revision 3 as of 2019-08-14 19:49:24
Size: 1674
Comment:
Revision 4 as of 2019-08-19 20:27:47
Size: 1849
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
  * Buildbot awareness and status.
    * How does one fix buildbot issues?
      * Who is responsible for each buildbot?
    * Who is responsible for fixing a regression?

GNU Cauldron 2019 Agenda

On XXXX 2019 the GNU C Library community held a BoF at GNU Cauldron 2019.

  • Buildbot awareness and status.
    • How does one fix buildbot issues?
      • Who is responsible for each buildbot?
    • Who is responsible for fixing a regression?
  • Contribution Checklist v2
    • Ask reviewers to give “Reviewed-by:” so we can thank them all.
  • GLIBC_PRIVATE mangling
    • Break applications using GLIBC_PRIVATE by mangling the symbol at every release or build?
  • latrace/audit integration
    • Merge latrace and ltrace?
    • Put it on gitlab, and call it part of the official glibc audit framework?
  • Put glibc on gitlab?
    • Inconvenient to move.
    • Adds a PR workflow for those that like that.
    • Still supports email-based workflow.
    • Faster access to repository via Gitlab's servers (tested faster than sourceware).
    • Provides CI hooks for running build-many-glibcs for each PR.
  • Building independent parts of glibc
    • A libglibcmalloc.so - Independent malloc for testing experimental changes?
    • A libm.so & libmvec.so - Revisit discussion?

  • Update the glibc build infrastructure
    • Discuss getting accurate dependency information into the build system so we can do incremental build and test in as fast a time as possible.
  • How do we, as a core library, promote research into:

GNU Cauldron 2019 Notes

Notes to go here.

None: Cauldron2019 (last edited 2019-09-25 17:32:45 by CarlosODonell)