Bioconductor 3.24 release checklist (25 November 2026)

Open
  • Is something wrong?
#283 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
release

Research direction

Start with the Bioconductor release schedule and the listed bugphyzz and bugphyzzExports issues, then follow the checklist in release order. Coordinate package checks, data export, NEWS and Zenodo updates, and the DOI change to the import default. Done means the 3.24 release has shipped and every applicable checklist item is complete.

Written by the indexing model from the issue text.

Description

Tracking issue for what ships in Bioconductor 3.24. Dates from the release schedule: release candidate 11 November, deadline for packages passing build and check 18 November, release branch 23 November, release 25 November.

Bioconductor's git devel is still at 1.7.1 (29 April); GitHub devel is 1.7.7, 21 commits ahead. The Zenodo deposit is the GitHub archive of the tag, and .downloadZ() reads every file matching "csv" from it, which now includes sources/bacdive/bacdive.csv.gz.

bugphyzz, before the 11 November release candidate
  • Push GitHub devel to git.bioconductor.org devel (1.7.8, 5 November); check the next devel build report
  • .downloadZ() reads only the three bugphyzz_*.csv files from the Zenodo zip
  • #256 bugphyzz: prefix in makeSignatures(), with a NEWS note that signature names change
  • #281 attributes.tsv clean-up (#284; the 56 ungrouped rows stay open)
  • #266, cheap half: \dontrun{} on the physiologies('all') example and skip_if_offline() on download tests; the fixture waits
  • Sheet fixes #260, #261, #262, #273
bugphyzzExports, data release
  • waldronlab/bugphyzzExports#83 AMR names validated before the rewrite
  • waldronlab/bugphyzzExports#64 decide on family-and-above rows (proposal: keep and document)
  • waldronlab/bugphyzzExports#66 point 1 only (source priority per confidence level) if it fits; points 2 and 3 after the release
  • Dispatch the export after the above; log_file.msg reports no dropped values
  • NEWS.md: date the 2026-11 section as v1.1.0 with the DOI; add #256 and #83
  • .zenodo.json creators (Wokaty, Andres)
  • Tag v1.1.0, GitHub release, Zenodo deposit; confirm the zip holds data, not LFS pointers, and importBugphyzz(version = "<DOI>") works
bugphyzz, after the DOI exists, before 18 November
  • New DOI as the importBugphyzz() default; roxygen, vignette and the pinned-DOI test updated
  • NEWS.md entry for the final 1.7.x and push to Bioconductor again
  • Tick the Zenodo line in waldronlab/bugphyzz-manuscript#10

Not in this release, already filed: waldronlab/bugphyzzExports#66 points 2 and 3, #266 fixture, waldronlab/taxPPro#15, #282, waldronlab/taxPProValidation#2. Close this issue when 3.24 ships.

Drafted with Claude Code.

Dominant language
R
Stars
6
Forks
6
Avg merge
1h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from waldronlab/bugphyzz

All issues in waldronlab/bugphyzz

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.