[Bioc-devel] Is version 1.1.0 correct for a new released package?

Thanks for your thorough answer. So, when I?m going to push the first devel change, the version must be 1.1.1 while bug fixes for the released package will start from 1.0.1. Am I right?



Best regards,

Arman



________________________________
From: Shepherd, Lori <Lori.Shepherd at RoswellPark.org>
Sent: Wednesday, November 1, 2017 9:49:40 PM
To: Arman Shahrisa; bioc-devel
Subject: Re: [Bioc-devel] Is version 1.1.0 correct for a new released package?


Yes this is correct -  Pkg_version x.y.z


We do a version bump on the devel version of the package to make the versioning consistent with release( y even in release)  - hence the first version bump to 1.0.0 -  this is now the current release version of your package


The second version bump is to make the versioning consistent in devel (y odd in devel) - hence the 1.1.0 - this is now the current devel version of your package.


We do this on our end when we make our Bioconductor release branches.



Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

________________________________
From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Arman Shahrisa <shahrisa.arman at hotmail.com>
Sent: Wednesday, November 1, 2017 2:14:54 PM
To: bioc-devel
Subject: [Bioc-devel] Is version 1.1.0 correct for a new released package?


Hi,

There are two GitHub commits for my package ?cbaf? by Bioconductor on 30 October.
The interesting thing is the first commit changes version in description file from
0.99.8 to 1.0.0 while the second one changes 1.0.0 to 1.1.0. Is it correct?
In Bioconductor.org the version of published package is 1.0.0. The same thing has happened
for Bioconductor git repository as well (After pulling the changes made by bioc team).

Best regards,
Arman


        [[alternative HTML version deleted]]


This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.


This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.