[Bioc-devel] Noticed change of version for some packages in BioC 3.2

Dan Tenenbaum dtenenba at fredhutch.org
Wed Mar 2 17:02:05 CET 2016


Have a look at

http://blog.revolutionanalytics.com/2014/08/gran-and-switchr-cant-send-you-back-in-time-but-they-can-send-r-sort-of.html
https://cran.r-project.org/web/packages/packrat/index.html

Dan


----- Original Message -----
> From: "Stefano Berri" <sberri at illumina.com>
> To: "Dan Tenenbaum" <dtenenba at fredhutch.org>, "Bernd Klaus" <bernd.klaus at embl.de>
> Cc: "bioc-devel" <bioc-devel at r-project.org>
> Sent: Wednesday, March 2, 2016 2:20:12 AM
> Subject: RE: [Bioc-devel] Noticed change of version for some packages in BioC 3.2

> Thank you very much for the info.
> 
> I didn't realised bug fixes and versions changes were allowed in release. And it
> is good to know in a month 3.2 will be frozen forever.
> 
> Do you then have a strategy to suggest for automating download and install
> packages in a very reproducible way? Am I right that if I leave package
> installation to R it won't be all that reproducible, especially when dependency
> relies on CRAN packages?
> 
> cheers
> 
> Stefano
> 
> 
>   
> 
>> -----Original Message-----
>> From: Dan Tenenbaum [mailto:dtenenba at fredhutch.org]
>> Sent: 01 March 2016 16:01
>> To: Bernd Klaus
>> Cc: Berri, Stefano; bioc-devel
>> Subject: Re: [Bioc-devel] Noticed change of version for some packages in
>> BioC 3.2
>> 
>> The main reason for packages to change in release is because of bug fixes,
>> also documentation enhancements.
>> 
>> You should not expect the versions in release to be frozen.
>> Dan
>> 
>> 
>> ----- Original Message -----
>> > From: "Bernd Klaus" <bernd.klaus at embl.de>
>> > To: "Stefano Berri" <sberri at illumina.com>, "bioc-devel" <bioc-devel at r-
>> project.org>
>> > Sent: Tuesday, March 1, 2016 3:48:21 AM
>> > Subject: Re: [Bioc-devel] Noticed change of version for some packages in
>> BioC 3.2
>> 
>> > Hi Stefano,
>> >
>> > developers are not supposed to change the package fundamentally in the
>> > release branch, however small fixes are allowed to be back-ported and
>> > marked by a bump of the last digit:
>> >
>> > http://bioconductor.org/developers/how-to/version-numbering/
>> >
>> > (E.g. fixing typos in the vignette or updating the citation
>> > information)
>> > As far as I know, only the url
>> >
>> >
>> > http://bioconductor.org/pckages/<packageName>
>> >
>> > is stable.
>> >
>> >
>> > Best wishes,
>> >
> > > Bernd



More information about the Bioc-devel mailing list