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

[Bernd Klaus]

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



itefano wrote:
> Hi.
> 
> Maybe I am getting something wrong, but I am pretty sure I noticed
> the change of package version for some Bioconductor packages in 3.2
> 
> In particular
> 
> -       IRanges_2.4.6.tar.gz \
> +      IRanges_2.4.8.tar.gz \
> -       Biostrings_2.38.3.tar.gz \
> +      Biostrings_2.38.4.tar.gz \
> -       rtracklayer_1.30.1.tar.gz \
> +      rtracklayer_1.30.2.tar.gz \
> -       GenomicFeatures_1.22.12.tar.gz \
> +      GenomicFeatures_1.22.13.tar.gz \
> 
> where [-] indicates what it used to work, [+] what it works right
> now.
> 
> For instance, url
> http://bioconductor.org/packages/3.2/bioc/src/contrib/IRanges_2.4.6.t
> ar.gz
> 
> worked a month ago but now it doesn't anymore and url
> http://bioconductor.org/packages/3.2/bioc/src/contrib/IRanges_2.4.8.t
> ar.gz
> 
> works instead
> 
> I thought that once the package collection have been released (3.2
> was released in October) that is frozen forever and changes only
> happen in the development release.
> 
> Am I missing something or got something wrong? At what point urls are
> considered stable?
> 
> Thank you very much
> 
> Best wishes
> 
> Stefano
> 
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel