Hey, > I think we already talked about it once. > sparse-opencl fails on my laptop's GT540m, and apparently here too: > https://github.com/viennacl/viennacl-dev/issues/105
Ok, strangely there is no regular failures in the nightly tests. Either way, 'partially working' isn't acceptable, I'll track it down ;-) > What do you mean exactly? Releasing on the same day? That's probably > not necessary, as it increases the chances of some unsync'd changes > at the last minute. Releasing pyViennaCL a few days after ViennaCL > is fine with me, but I'd say that this primarily depends on Toby :-) > > > Well yes. I thought it would be better to have a mutual announcement for > both the library and the wrapper. Just my opinion, though! Announcements usually stick in the various queues for a couple of days, so as long as ViennaCL and PyViennaCL get released within, say, a week, we can still announce both of them together in the various channels. Actually, I suggest to release ViennaCL 1.6.0 first (end of next week) and then finish up PyViennaCL as well as the benchmark GUI the days after. Toby, is this possible for you? Best regards, Karli ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
