-
Notifications
You must be signed in to change notification settings - Fork 13
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
Coordinate R Versions with Bioconductor #40
Comments
We're targeting R 4.4.1 for HADES-wide release 2024Q3. Our current process for selecting the next R version to support is based on balancing site ability to upgrade, and whether the update is required to run HADES. I agree it would be nice to mirror Bioconductor, but not at significant cost to sites to force them to upgrade without a clear need. Do you know what process Bioconductor uses to determine the R version to support next? |
Bioconductor's devel branch uses different R versions throughout the year After R's release in April/May until Bioconductor's release in Oct/Nov:
From Bioconductor's release in Oct/Nov until the next R release:
During the R-devel period:
|
Thanks Hayden! I think BioConductor's pace of updating is higher than we want it to be for HADES. |
Currently it is necessary to use two versions of R when working with both HADES and OHDSI tooling alongside Bioconductor.
HADES 2024Q1 Wide Release: R Version 4.2.3
Bioconductor Version 3.19: R Version 4.4
Alignment of R versions would allow for a single R installation that would cover a considerable range of informatics work.
HADES developers could develop against the Bioconductor devel R version with a reasonable expectation that this would become the next HADES wide release R version (and bio conductor release version).
The text was updated successfully, but these errors were encountered: