Hi Graham,

On 3 April 2020 at 20:07, Graham Inggs wrote:
| Hi Dirk
| 
| On Sat, 28 Mar 2020 at 15:57, Dirk Eddelbuettel <e...@debian.org> 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.

Thank you.

I am still (as always) lost by the process. Does that mean an upload to
unstable is now ok?  Or not?  I am unsure what "hand shake" from the ftp /
release team I should be waiting for.

| Packages marked [arch:all] will need uploads by the team / maintainer,
| the rest can be handled by binNMU.

Can the tracker sort by
 - maintainer
 - binary type
to help ?
 
| > 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)?

I do not know. I am much less involved in matters BioC but follow R business
relatively closely. It all starts with my r-base package, after that we
"merely" have to walk the dependency tree.

Someone with more BioC clues (Charles?) may know better if you should for new
upstreams from BioC or update what is in testing -- which I would upgrade as
they /will/ fail to run / install / migrate due to r-3.5 and r-4.0 tags.

| Please keep this bug in replies.

Sure.

Cheers, Dirk

| 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

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to