search

r-universe-org / help

Support and bug tracker for R-universe
https://docs.r-universe.dev/
9 stars 2 forks source link

Show CRAN and Git(hub) Version Difference #82

Open eddelbuettel opened 3 years ago

eddelbuettel commented 3 years ago

There is no (formal) link between (actual, fixed, tarball) releases at CRAN and the universe.

But there is a visual display on the dashboard if the CRAN package signals the git(hub|lab|...) repo used in universe.

That is fine but it can be mildly misleading when the git repo departs (advances ahead) from the CRAN release.

You do have the CRAN release version, and the package version you build here. I think it would help quite a bit if you could use, say, colour to differentiate. I still like blues, so maybe print the version number (or that CRAN check logo) in blue if they align, and use a different shade of blue (lighter? darker?) if the version in git is ahead of the CRAN version. (And/or an orange-ish warning color if the git repo is behind, if that ever happens?)

eddelbuettel commented 6 months ago

I would like to revisit this issue. I (with my other hat on) get a lot use out of a Debian aggregation dashboard. It serves many purpose: chiefly build and bug status, but also 'currentness' using the debian/watch file. One item that helped me spot a 'forgotten git push' is that the git repo column actually signal whether the git repo is ahead or behind the package.

So it would be pretty cool if 'binary' status of 'yes, this r-universe build is the one for the CRAN package of the same name' could also signal if the version is ahead, the same, or behind. Different shases of green? Different color if behind?

I am bringing this because the pattern of 'prepare upload to CRAN, do not yet push until heard from CRAN' is error prone in that we all can forget to actually sync to Github once a package is on CRAN. Catching a simple visual alert from r-universe might help a fair amount methinks.