On Jun 5, 2018, at 11:59 AM, Samsiddhi Bhattacharjee <sb1 at nibmg.ac.in> wrote:
I was thinking to have an onAttach mentioning the issue and directing the user to use the devel version to get around the issue...is that possible?
----- Original Message -----
From: Turaga, Nitesh <Nitesh.Turaga at RoswellPark.org>
To: Samsiddhi Bhattacharjee <sb1 at nibmg.ac.in>
Cc: Bioconductor Packages <maintainer at bioconductor.org>
Sent: Tue, 05 Jun 2018 19:45:18 +0530 (IST)
Subject: Re: Reverting to older version
Hi Samsiddi,
You can push a bug fix back to your release version RELEASE_3_7 and alert users of the release version within your .onAttach() message. This is usually done only if the bug fix is important enough to be back ported to a release.
Otherwise, you would just continue your development on the ?development? version (master branch) of your repository. Issue a version bump along with your bug fix.
Relating to your second question, any user using the ?devel" version of Bioconductor will get the latest version of your package. You may also choose to send them a GitHub link and let them install through that, but installing via Bioconductor is recommended.
Best,
Nitesh
On Jun 5, 2018, at 5:29 AM, Samsiddhi Bhattacharjee <sb1 at nibmg.ac.in> wrote:
Hi Nitesh,
Thanks for the detailed response. A naive question.. Is it like the .onAttach() can be pushed to release version right away? Or will it go in the
October release?
Also, in the meantime what would be the easiest way for somebody to install the devel version of our package (assuming we change it to 1.19.1) ? Should we send them github link ?
Thanks and regards,
--
Samsiddhi
----- Original Message -----
From: "Nitesh Turaga" <Nitesh.Turaga at RoswellPark.org>
To: "Samsiddhi Bhattacharjee" <sb1 at nibmg.ac.in>
Cc: "Bioconductor Packages" <maintainer at bioconductor.org>
Sent: Wednesday, May 23, 2018 9:09:35 PM
Subject: Re: Reverting to older version
Hi Samsiddhi,
You should implement the changes in the devel branch as v. 1.19.1 or maybe 1.99.0 (if next release you want is version 2.0.0).
You could also consider adding a message in .onAttach() of current release package to indicate what the issues are with the release. You could also introduce bug fixes into the release. You do NOT want to revert the version number to something previous.
Bioconductor packages do not go backwards in time using version control. Please introduce you changes as a new version and push to Bioconductor and GitHub(if you maintain a version on Github).
Best,
Nitesh
On May 23, 2018, at 9:28 AM, Samsiddhi Bhattacharjee <sb1 at nibmg.ac.in> wrote:
Hi,
We have recently discovered some issues (most importantly computational speed issues) with recent versions of our package and wanted to revert to an older version ASSET version 1.8.0 present in Bioconductor release 3.2. Is it possible to do? Please let me know the process.
Thanks and regards,
--
Samsiddhi
(ASSET maintainer
on github: sbstatgen)
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.