config.yaml: (Bioconductor, R) mapping for Bioconductor 1.0-1.5?

[HenrikBengtsson]

The config.yaml file specifies (Bioconductor, R) mappings for Bioconductor (>= 1.6);

bioconductor.org/config.yaml

Lines 123 to 125 in f8a0142

	r_ver_for_bioc_ver:
	"1.6": "2.1"
	"1.7": "2.2"

However, https://github.com/Bioconductor/bioconductor.org/blob/master/content/about/release-announcements.md provides such mappings from Bioconductor 1.0:

Release	Date	Software packages	R
1.6	May 18, 2005	123	2.1
1.5	October 25, 2004	100	2.0
1.4	May 17, 2004	81	1.9
1.3	October 30, 2003	49	1.8
1.2	May 29, 2003	30	1.7
1.1	November 19, 2002	20	1.6
1.0	May 1, 2002	15	1.5

Is there a reason for the latter being left out from the config.yaml file? If not, I can do a PR if you'd like.

[mtmorgan]

I can't think of a good reason why the config.yaml file couldn't be extended in this way. Probably there is infrastructure that is supported at 1.6 and beyond (biocLite?) but that seems like ancient history...

[HenrikBengtsson]

Thanks. I've created PR #97 that fills the gap.

[lshep]

The S3 archive of packages has Bioc 1.8 and greater. The release announcements only have from Bioconductor 1.5 and there is a mechanism for download for (at least my attempt at one of) the packages. I looked at aCGH release in Bioconductor 1.5 and there is a source tarball downloaded. The landing pages and where we store package archives I believe changed over time.
I'm not sure if we could even get versions of lower than Bioconductor 1.5 since there doesn't seem to be landing pages or any reference to the package versions, or what packages were released under those releases, to know which to download. Did we still want to include those in the configuration anyways @mtmorgan .