Skip to content

[Bioc-devel] Okay to push a hotfix for an existing release?

4 messages · Nanda, Pariksheet, Shepherd, Lori, Marcel Ramos

#
Hello,

I was wondering whether someone from the Bioconductor core team might reply to this e-mail and/or to this GitHub issue [1] to confirm Bioconductor's hotfix policy. Specifically, the web server that JASPAR2024 relies on has changed and the old server SSL certificate expired on 2024-08-31 that breaks the package. It would be great if someone could confirm it's okay to apply the bug fix outside of the typical release cycle to the current release branch. I don't see this hotfix edge case in the general contributor guidelines [2] though of course I may have overlooked it mentioned elsewhere.

Thank you for any help,
Pariksheet

[1]  https://github.com/da-bar/JASPAR2024/issues/3
[2] https://contributions.bioconductor.org/versionnum.html
#
Yes if it is a bug fix and required for the package to function properly, It is okay to push to the RELEASE_3_20 branch.



Lori Shepherd - Kern

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263
1 day later
#
Hi Pariksheet,

Thanks for pointing this out.
I have created an issue regarding this scenario here: 
https://github.com/Bioconductor/pkgrevdocs/issues/130
and we will add more details at https://contributions.bioconductor.org

To answer your question, yes, the package should be updated in the 
release and devel branches so that it remains functional.

Best regards,

Marcel
On 12/2/24 10:07 AM, Nanda, Pariksheet via Bioc-devel wrote:
____

*Marcel Ramos, MPH*
Sr. Data Scientist

CUNY Graduate School of Public Health & Health Policy
55 W. 125th Street, 6th Fl.| New York, NY 10027
marcel.ramos at sph.cuny.edu <mailto:marcel.ramos at sph.cuny.edu> | (646) 
364-9585
sph.cuny.edu <https://sph.cuny.edu>