On 06/11/2015 11:50 AM, Hervé Pagès wrote:
Hi Stephanie,
On 06/11/2015 11:33 AM, Gabe Becker wrote:
Stephanie,
As far as I know, it is so that package versions are unique to specific
releases of bioconductor. This has the benefits of
1. providing assurances that that particular version of
Hi Stephanie,
On 06/11/2015 11:33 AM, Gabe Becker wrote:
Stephanie,
As far as I know, it is so that package versions are unique to specific
releases of bioconductor. This has the benefits of
1. providing assurances that that particular version of a package is
tested and confirmed to wo
Stephanie,
As far as I know, it is so that package versions are unique to specific
releases of bioconductor. This has the benefits of
1. providing assurances that that particular version of a package is
tested and confirmed to work within that release, and
2. enforces that the source cod
Why is it that packages with no changes still get new version numbers at
every release? For example, my experiment data package GWASdata has not
changed since the last release, but the version was bumped from 1.4.0 to
1.6.0. I imagine most users expect that a change in version number
indicates
