The Bioconductor Release 3.17 Schedule has been posted and is tentatively 
scheduled for Wednesday April 26. This date is subject to change. Bioconductor 
3.17 will use R-4.3 scheduled to be release Friday April 21.


Important deadlines can be found on the website 
<https://bioconductor.org/developers/release-schedule/> and will be posted here 
and on the bioc-devel at r-project.org mailing list. As a quick summary:


Friday March 31: New package submission deadline. Packages will still need to 
pass the formal review process to be included in Release 3.17; this deadline 
will ensure at least an initial review of the package. Package submitted after 
this date are not guaranteed to be reviewed; they will be reviewed time pending.


Wednesday April 5: No API changes to devel 3.17.


Monday April 10: Current Release 3.16 Freeze. No changes will be accepted to 
the Bioconductor 3.16 branch after this date.


Wednesday April 19: Newly submitted packages need to be accepted by this date 
to be included in the release


Friday April 21: Deadline for packages to be passing R CMD install/build/check 
on Bioconductor builders.


Tuesday April 25: Devel 3.17 branch is frozen to create release branch.


Wednesday April 26: Release Bioconductor 3.17


Cheers,


 Lori Shepherd on behalf of the Core Team

https://bioconductor.org/developers/release-schedule/


This email message may contain legally privileged and/or confidential 
information.  If you are not the intended recipient(s), or the employee or 
agent responsible for the delivery of this message to the intended 
recipient(s), you are hereby notified that any disclosure, copying, 
distribution, or use of this email message is prohibited.  If you have received 
this message in error, please notify the sender immediately by e-mail and 
delete this email message from your computer. Thank you.
        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

Reply via email to