gt; To: "Dan Tenenbaum" <dtene...@fredhutch.org>, "Bernd Klaus"
> <bernd.kl...@embl.de>
> Cc: "bioc-devel" <bioc-devel@r-project.org>
> Sent: Wednesday, March 2, 2016 2:20:12 AM
> Subject: RE: [Bioc-devel] Noticed change of version f
> 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 ver
Berri" <sbe...@illumina.com>, "bioc-devel"
> <bioc-devel@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 ch
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
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 \
-
