Dear Lori,
Thank you – and sorry I missed this in the documentation. I will not be
creating the RELEASE directory and just push to master.
Cheers
Matteo Tiberti
Danish Cancer Society
Strandboulevarden 49
DK-2100 Copenhagen
Telefon: +45 35 25 73 07
If you are running locally, there is also a .BiocCheck folder that
gets created with a log that has the more specific information as well.
Cheers,
Lori Shepherd - Kern
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm &
There is no RELEASE_3_16 branch yet. Bioc 3.16 is still considered devel;
release branches are only created at release time. Do NOT create it yourself;
this is done by the core on git.bioconductor.org at release time. To update
devel you would push to master.
All of this is very well
Dear maintainers,
I’d like to push a commit (and a version bump commit) to fix our build report
error for our MoonlightR package, for the current development version 3.16. If
I understood correctly, I would need to push directly to the RELEASE_3_16
branch in upstream (Bioc remote) which
