Hi Toby, >> 1.) Toby, how's the status with PyViennaCL? What is missing for a release? > > No code is missing, but some documentation is, mostly finishing off the > new parts added during GSoC. I'm slowly making progress, but I will > probably need another 7-10 days for this, as busy as I currently am! I > wonder if it might be better to release PyViennaCL with ViennaCL 1.6.1, > which I can imagine being ready before I am.
yeah, having pyViennaCL based on ViennaCL 1.6.1 makes sense, as we found (an eliminated ;-) ) a couple of nasty bugs sind the 1.6.0 release. >> 2.) We currently use viennacl.sourceforge.net as a common domain. >> However, I wonder whether it better to use three separate domains for >> better managing the projects? What about using e.g. >> pyviennacl.sourceforge.net >> viennaclbench.sourceforge.net >> for PyViennaCL and the benchmark GUI? Any thoughts? > > I'm quite happy with this. Philippe was talking recently in terms of a > 'ViennaCL ecosystem', and I think this follows that pattern. Fine - so it seems like we have a majority here :-) Best regards, Karli ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
