Re: [easybuild] Version numbering for new CUDA toolchain

2016-08-24 Thread Eliot Eshelman
Thanks for the comments, Davide! I'll use your numbering if no one else objects. My builds all look good, so I'm ready to submit the pull request. Or were you about to do so yourself? I was hoping Kenneth would jump in and tell us if we're right or wrong. We can always adjust before he

Re: [easybuild] Version numbering for new CUDA toolchain

2016-08-24 Thread Eliot Eshelman
Agreed! I know the CPU-only toolchains have gone to date-based numbering. I'd be happy to switch this, too! I recommend we call this 2016.08. By the time CUDA 8.0 comes out, we'll be able to call that one 2016.09. Eliot On 08/24/2016 11:02 AM, Maxime Boissonneault wrote: Hi everyone,

Re: [easybuild] Version numbering for new CUDA toolchain

2016-08-24 Thread Vanzo, Davide
Eliot, please proceed with the pull request whenever you want. I am currently on hold until I get some advice on how to deal with naming MPI easyconfigs for different networks. I will be happy to test your pull whenever available. Davide On Aug 24 2016, at 9:58 am, Eliot Eshelman

Re: [easybuild] Version numbering for new CUDA toolchain

2016-08-24 Thread Maxime Boissonneault
On 16-08-24 11:48, Vanzo, Davide wrote: Maxime, I agree that the current toolchain version numbering is quite confusing. One question about date numbering: what if somebody wants to downgrade one of the toolchain elements? Maybe a micro version number would still be useful for this task.