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.
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
Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
version 2.3.6
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.
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.