Why git links at the bottom of a package of the current release point to the devel code?
1
0
Entering edit mode
SamGG ▴ 270
@samgg-6428
Last seen 5 weeks ago
France/Marseille/Inserm

Hi,

I am trying to propose a PR to a package of the current release but I fall back to the devel code.

I will go with the gz file of the current release, but this does not sounds coherent to me.

Best.

Bioconductor • 195 views
ADD COMMENT
0
Entering edit mode
shepherl 2.8k
@lshep
Last seen 16 hours ago
United States

Unless this is a bug fix, PR and feature requests are generally always applied to the devel code. If you are checking out the git.biocondcutor.org repository for a package, the master branch is equivalent to the devel code base. If you git fetch --all you should be able to see the other branches like the current RELEASE_3_12 that would have release code

ADD COMMENT
0
Entering edit mode

Plus the PR would have to be applied to devel too, if applied to release. so it would be a better practice to develop on devel and only import to release if absolutely necessary.

ADD REPLY
0
Entering edit mode

Thanks for your feedback.

To be coherent with this policy, there should be no link to git but a link to the devel page of the package, IMHO.

Currently the devel version of the package does not compile on my platform, so it is difficult correct anything. That's why I fall back to stable release that I can compile and install.

Best.

ADD REPLY

Login before adding your answer.

Traffic: 432 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6