Dear all,
Thanks a lot for your help. I managed to commit the new version of the
package to the release branch.
Many thanks again for your replies.
Best,
Sandro
On 3 Mar 2016 16:28, "Dan Tenenbaum" wrote:
> You can merge from devel into release (as long as it's only bug fixes),
> but make sure yo
You can merge from devel into release (as long as it's only bug fixes), but
make sure you don't overwrite the version number. If the version number in
release was 1.0.0 before the merge, make sure it is 1.0.1 before committing.
See https://www.bioconductor.org/developers/how-to/version-numbering
Hi Sandro,
The devel and release repositories are distinct.
RELEASE:
svn co
https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_3_2/madman/Rpacks/VegaMC
DEVEL:
svn co https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/VegaMC
Work on the two should be kept separate, ie, to work on
Ha, Thanks, Dan.
Best,
On 08/01/2014 01:39 PM, Dan Tenenbaum wrote:
You can't commit to release 2.13 since we are no longer building it. You can
commit to the current release branch (2.14) and to trunk (devel).
Dan
- Original Message -
From: "Chen Meng"
To: bioc-devel@r-project.org
You can't commit to release 2.13 since we are no longer building it. You can
commit to the current release branch (2.14) and to trunk (devel).
Dan
- Original Message -
> From: "Chen Meng"
> To: bioc-devel@r-project.org
> Sent: Friday, August 1, 2014 3:41:21 AM
> Subject: [Bioc-devel] sv
