Hello,
I maintain the ClusterSignificance package which recently encountered a build
fail. While investigating the problem I noticed that it would seem that there
is an issue with the version numbering (quite possibly my fault). Both the
master and RELEASE_3_7 branches were bumped to version 1.
Lori,
Thanks for your quick response! Ok, it was the fact that
https://git.bioconductor.org/packages/ClusterSignificance is devel by default
that was not clear to me (potentially obvious in hindsight). Thanks for
clearing this up!
Kind Regards,
Jason
On 10 Jul 2018, at 11:41, Shepherd, Lori
There is no problem with the versions.
The master branch is the devel branch - and the DESCRIPTION on our git server
is 1.9.0
The RELEASE_3_7 branch is the release 3.7 branch - and the DESCRIPTION on our
git serve is 1.8.0
When you clone the repository git clone
https://git.bioconductor.or
Hi,
We don't have a date yet but it will probably be in October (not necessarily
the 31st).
Valerie
On 07/09/2018 11:34 PM, Samuel Wieczorek wrote:
Hi
I am the developer of the packages DAPAR and Prostar. I have to plan in
advance some work and I would like to synchronise this with the nex
Dear Martin,
The updates that I made to man files are not reflected in the manual of
the package (release 3.7) :
https://bioconductor.org/packages/release/bioc/manuals/BiFET/man/BiFET.pdf
In fact, I found that all files in the release_3_7 are old files that were
not updated since January and not
For RELEASE 3.7 you need to push changes to the git.bioconductor.org
repository RELEASE_3_7 branch with a version bump to 1.0.1. See
http://bioconductor.org/developers/how-to/git/maintain-bioc-only/#optional-merge-changes-to-the-current-release-branch
remember that changes to the release branc
