Hi Ken, On Dec 17, 2013, at 2:15 PM, Kenneth Hoste wrote: > Considering all opened PRs is going to push back the release too much, so if > you would really like to see particular PRs included in EasyBuild v1.10, > please push them forward in this thread ASAP.
OK, from my side, I'd vote for (in rough order of priority): https://github.com/hpcugent/easybuild-easyconfigs/pull/585,587,589,591 # It is 1 split PR for ictce-5.3.0 https://github.com/hpcugent/easybuild-easyconfigs/pull/552/files # massive templates fix https://github.com/hpcugent/easybuild-easyconfigs/pull/600/files # Lua/Lmod, good for bootstrapping EB https://github.com/hpcugent/easybuild-easyconfigs/pull/582/files # Coreutils; others need it https://github.com/hpcugent/easybuild-easyconfigs/pull/560 # Generic Mapping Tools (dep: #547) https://github.com/hpcugent/easybuild-easyconfigs/pull/596/files # gperftools, delivers libunwind (hint: UNITE) https://github.com/hpcugent/easybuild-easyconfigs/pull/610/files # povray, delivers libjpeg-turbo On CUDA front, if you'd benefit from these, let's add in: https://github.com/hpcugent/easybuild-easyconfigs/pull/571 # PyCUDA https://github.com/hpcugent/easybuild-easyconfigs/pull/489 # Tesla Deployment Kit https://github.com/hpcugent/easybuild-easyconfigs/pull/546 # Rgputools The last one has received lot of effort, should be near-final, yet I am pragmatic... On bioinfo front, be my guest to choose whatever is convenient and others desire: https://github.com/hpcugent/easybuild-easyconfigs/pull/592 # GATK https://github.com/hpcugent/easybuild-easyconfigs/pull/568 # FSA, Prank, SMALT, Infernal btw. Jens had contrib'd somewhere intel-built Cufflinks, that would be good to include. Also, to help you in sorting out the mess (most of these are NOT mine ;-) : https://github.com/hpcugent/easybuild-easyconfigs/pull/619 & 579 # BEDTools; @pescobar, @jens? https://github.com/hpcugent/easybuild-easyconfigs/pull/540 & 556 # Erlang, OCaml The last might benefit just from some commenting on how to merge/align the two PRs. Don't complain they are many, it was you asking for "mroe software, mroe PRs" ;-) > I hope I can get to handling the other PRs quickly after the release, and we > will look into automating the testing process further to lower the overhead > of incoming PRs. What would help all of us, is to let Jenkins auto-test incoming PRs and have a filtered-view of the ones that pass Jenkins testing. It would turn looking at open PRs less scary and far more tractable. *That* subset should be the _only_ one to consider in a merge-window! (save for documented cross-deps, like in the ictce/5.3.0 sets mentioned above) cheers, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
