Maybe a little more helpfully, I think you should create a branch for 'before' Bioconductor, where you can specify R version dependency as you see fit.
Indeed, at each release the version of your package at git.bioconductor.org will have a branch created for that release, e.g., the RELEASE_3_8 branch, and you will want to sync that branch with your github repository as outlined in step 10 of https://bioconductor.org/developers/how-to/git/sync-existing-repositories/ .
A conscientious developer would take the opportunity to increment the version dependency of R in the master branch to the version of R in use in the devel builds of Bioconductor.
Martin
?On 1/14/19, 5:40 PM, "Bioc-devel on behalf of Lulu Chen" <bioc-devel-bounces at r-project.org on behalf of luluchen at vt.edu> wrote:
Dear all,
When submitting package to bioconductor, it is required to change R version
in "Depends" to be >= the develop version (3.6) . As my package is also
available in GitHub, someone asks if it be possible to make it available
with the stable version of R (R3.5). In fact, my package can work well with
R3.5 if I change "Depends" back to R(>=3.5) .
So I hope to support R3.5 for the moment before next release. Should I
create another repository? Can I use a branch to support R3.5?
Thanks,
Lulu
_______________________________________________
Bioc-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel