Hej, Karl Rupp <r...@iue.tuwien.ac.at> writes: >> 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?
Yep, this is what I've been intending anyway :) Cheers, T ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
