Hi Jo, On 2026-10-19 at 16:49+00:00, Johannes Bartunek wrote: > I expected things like browser updates that contain fixes > for public CVE's to be merged quicker.
Good news for you/us: the team maintaining the browser packages just gained a new committer! On 2026-10-19 at 16:49+00:00, Johannes Bartunek wrote: > it saddens me that updates are not merged within a timeframe > of say 1-2 days and to see all of this energy pile up as backlog. Unfortunately, I don't think this is going to change in the near future. Trivial updates of packages which few other depends on and are light to build (say, 15 minutes in total on a personal computer) might get a chance, however, * Some are complex and takes a long sit to review. * Some are costs too much resources (time/memory) to build locally. * Some requires a higher level of QA, e.g. things people use for work, in services, or backup that shouldn't break any use case. Any of the listed categories (and more that I may miss) requires some volunteers to dedicate a significant amount of time and energy to read through the diffs, upstream change logs, build locally, and test manually. Personally I expect that to happen in 1-2 weeks. In addition, reviews are requested based on team scope, and many packages are orphaned. With ~17 new PRs every day, most people are unlikely to be aware of each new one. On 2026-10-19 at 16:49+00:00, Johannes Bartunek wrote: > is there anything I as a newcomer could do > to help [keep packages up to date]? You can help by reviewing and (later, as you mention being new to the community) joining some teams. Pulling some stats from https://guix.gnu.org/en/blog/2026/one-year-with-codeberg/ we have around 30 active committers each month, which extrapolates to around 50 reviewers (based on the team member/committer ratio), handling ~500 pull requests, not the mention the fixes landing directly on topic branches. Any addition of regular reviewers helps a lot, so tell your frens about Guix too! Cheers, Phong
