[Bioc-devel] Request to rename devel-only package BamScale to BamScaleR before the 3.24 release
Chirag Parsania
ch|r@g@p@r@@n|@ @end|ng |rom gm@||@com
Fri Sep 4 04:52:22 CEST 2026
Dear Bioconductor core team,
I maintain BamScale, which was accepted on 4 May 2026 (Bioconductor/Contributions issue #4128) and is currently in the 3.24 devel nightly builds at version 0.99.14. The package has never been part of a Bioconductor release.
I would like to rename it to BamScaleR before the 3.24 release. The reason is [REASON, e.g. to avoid confusion with the existing BAMscale command-line tool from NCBI (github.com/ncbi/BAMscale), which does something different]. I have checked that BamScaleR does not exist on CRAN or in Bioconductor (BiocManager::install("BamScaleR") fails and the name is absent from the 3.24 manifest).
I am aware that the guidelines describe renaming as deprecating the old package and resubmitting the new one for review. Since BamScale has not been in any release, there are no users to protect with a deprecation cycle. I noticed the same situation was handled by renaming the repository directly for SingleRBookWrapper -> SingleRBook (Contributions #1609) and scTypeR -> scClassifR (Contributions #1798), and I hope the same is possible here.
Concretely, could you:
1. rename packages/BamScale to packages/BamScaleR on git.bioconductor.org,
2. update the entry in the 3.24 software manifest,
3. update the push-access configuration so my SSH key maps to the new repository,
4. let me know whether I should push the renamed DESCRIPTION before or after
your change.
On my side I will rename the GitHub repository (cparsania/BamScale -> cparsania/BamScaleR), change the Package field and all internal references (useDynLib, native routine registration, vignette, documentation, URLs), bump to 0.99.15, and push to the renamed upstream to trigger a build. The version will stay in the 0.99.x pre-release series.
I would like to complete this well before the release branch for 3.24 is created, so the renamed package gets clean nightly builds first. If you would rather I go through the deprecate-and-resubmit route via BiocContributions instead, I will do that, though I would hope to avoid missing the 3.24 release.
Thank you very much for your help.
Best regards,
Dr. Chirag Parsania
Maintainer, BamScale
https://github.com/cparsania/BamScale
[[alternative HTML version deleted]]
More information about the Bioc-devel
mailing list