Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

srcmgr minutes #14

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions srcmgr/20241115.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# 20241115 srcmgr meeting

Attendees: markj, jhb, emaste, imp

Agenda:
- Warner posted a review to add the srcmgr charter
- https://reviews.freebsd.org/D47573
- Mark finished a draft email to developers@ soliciting work on tools
- Would like a couple more ideas
- Warner needs to provide some details on his github PR landing tool
- Mark is still working on the src bug triage guide
- cperciva@ asks, what do we need to be tracking for 15.0?
- Ed replied with some details
- pkgbase
- pkg fixes
- tooling to convert existing systems
- installer patches
- i386/powerpc32 retirement
- which OpenSSL LTS version will be in 15?
- 3.0 won't be in support for long enough
- should move to 3.3 or 3.4 before 15.0 is branched, but these are not LTS
- drm drivers in base
- spent time reviewing and updating the 15.0 planning doc from bsdcan
16 changes: 16 additions & 0 deletions srcmgr/20241129.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# 20241129 srcmgr meeting

Attendees: markj, emaste, imp

- A bit time-constrained today since it's US Thanksgiving
- Took in grehan@'s bit for safekeeping
- Discussed a bug triage session
- linimon@ has been closing many old bugs that have some commit associated with them
- sometimes this is incorrect, e.g., when a bug is opened for a test failure and we reference the bug in a commit which skips the test for CI
- mused having a "Fixes PR:" tag to make it easier to understand the relationship between the commit and the PR
- not sure we want to impose extra process; we might also confuse github in the future since "PR" is overloaded
- Going to host a src bug triage session on Friday Dec 6, 11am-2pm EST
- markj to send out a notification to developers@ on monday or tuesday
- emaste will help set up zoom
- Spent some time going through open PRs on github
- imp landed a whole bunch