Hi Dirk On Sat, 28 Mar 2020 at 15:57, Dirk Eddelbuettel <[email protected]> wrote: > R does change internals every now and then with the annual releases; this is > a major one which will require rebuilds of all packages.
I've set up a transition tracker [1] where we can see the magnitude of the transition. Packages marked [arch:all] will need uploads by the team / maintainer, the rest can be handled by binNMU. > R 4.0.0 will be released on April 24. The upstream team always follows a > well-publicised schedule >From the schedule [2]: * Tuesday 2020-03-24: START * Friday 2020-03-27: GRAND-FEATURE FREEZE (4.0.0 alpha) * Friday 2020-04-10: FEATURE FREEZE (4.0.0 beta) * Friday 2020-04-17: CODE FREEZE (4.0.0 RC) * Tuesday 2020-04-21: PRERELEASE * Friday 2020-04-24: RELEASE (4.0.0) I read on the debian-r mailing list that a parallel transition of Bioconductor will also be needed [3]. Would there be any point to starting the r-base transition much before the release of Bioconductor (2020-04-28)? Please keep this bug in replies. Regards Graham [1] https://release.debian.org/transitions/html/r-api-4.0.html [2] https://developer.r-project.org [3] https://lists.debian.org/debian-r/2020/04/msg00000.html
