The deadline for fixing packages in preparation for the release is this Friday October 20th. All packages should be installing, building, and checking without ERROR in the Bioconductor build report. While you can continue to push changes past this date, this ensures all changes are reflected in at least one build report before the code freeze for release. Packages that continue to show ERRORs in the build report after the release will be consideration for deprecation. We are on schedule to release Wednesday October 25th.
Please also remember to update your NEWS files for any information about changes to your packages during this last development cycle. Bioconductor collates all package news files as part of the release announcement. If your NEWS file is not formatted correctly and not updated by this weekend, it will not be included in the release announcement.
For clarification: The release 3.18 branch has not yet been created. Please continue to update the devel branch. Next week when the release occurs the core team will automatically create the RELEASE_3_18 branch on git.bioconductor.org but until that time the only branch accessible is devel. Do NOT try to create a RELEASE_3_18 branch on your own; the core team will do this for you. Bioconductor will also handle bumping the y of a package version x.y.z on release day.
My package vignette for
categoryCompare
currently depends on theestrogen
data package, which itself depends ongenefilter
, which at some point was not building, makingestrogen
unavailable for v 3.18. Should I just wait on the next build report, or take further actions to make sure my vignette builds?Regarding the URL 403 issue, I actually can't reproduce that locally, unfortunately. I suspect that what may be happening is that the
KEGGREST
package when it fetches the annotations for the genes, hit a limit on KEGG, or something else?? I also see the same error on Linux for 3.17.That does say something about either removing the
KEGGREST
explicit example, or caching a set of results for use in the vignette. I'm also considering loading the DEG results that right now useestrogen
from a file instead of working through it all in the vignette.Just chiming in regarding your remark on the URL 403 issue and
KEGGREST
: I also recently repeatedly experienced this 'error 'while using theKEGGREST
package, and I reached out to the KEGG helpdesk. They informed me that this is indeed due to a protection system that is activated when too many requests are made to their server.