On 05/05/2013 04:40 AM, Erik Schnetter wrote: > I was volunteered to manage the pocl 0.8 release. In my world, this means > that I > do the leg work, and seek community consensus for every decision that is > important.
Thanks for this, Erik. > At the moment we need to do three things: > (1) Decide which major features we want in pocl 0.8; once these are in and > tested, we would be ready to create a release branch IMHO the release should be time based tied to the LLVM release schedule. That is, we should not wait for new features unless someone commits to get them in within that time based schedule. Otherwise the release might drag on for too long. > As pocl is a volunteer project, each release criterion needs to be backed up > by > a volunteer who is looking into this. Please consider this when adding to the > criteria, I would prefer to only have criteria with a name listed next to it. That's a good idea. I volunteered to x86/Linux, x86-64/Linux and TCE. > I expect a release in a few weeks, shortly after the LLVM 3.3 release. Here's the email announcing the tentative Clang/LLVM release schedule: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2013-May/029424.html -- --Pekka ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
