Hi Martin
good to see that Herve agrees with me, and I reiterate my point, because
I consider this issue very important.
The average user does _not_ expect that a function like 'biocLite',
which has the express purpose of downloading and installing packages,
does not pull the newest package.
Hi
I second improving the awareness of users about new Bioc releases and
also personally do not mind loud messages while I am
installing/upgrading packages, even if it is each time I source/run
biocLite(). Indeed for old releases that I maintain for old projects
very rarely have to install a new p
Martin, Herve, Simon, et al,
i see a straightforward approach without the need to change biocLite()
or BiocInstaller behavior. what about every package deciding in loading
time to tell or not the user whether he/she should be using the latest
version of the package, if he/she is not using it?
Hi,
there is benefit in having newest versions, but I think we shouldn't get
carried away, and find Martin's suggestion reasonable. I don't want to be told
to go get an iPhone 5 every time I update an app on my iPhone 4 - even if that
same app would work much better there. People may have legiti
Hi
however unlike an iphone Bioconductor is only (as far as I know)
supported for the current release. We all do our best to help users
when they find problems and in most cases when I have suggested they
upgrade they have done so- solving their problems. If they were more
aware of being using an
