From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31109 invoked by alias); 26 May 2013 07:28:53 -0000 Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org Received: (qmail 31072 invoked by uid 89); 26 May 2013 07:28:48 -0000 X-Spam-SWARE-Status: No, score=-6.2 required=5.0 tests=BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,SPF_PASS autolearn=ham version=3.3.1 Received: from gw01.mail.saunalahti.fi (HELO gw01.mail.saunalahti.fi) (195.197.172.115) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 26 May 2013 07:28:44 +0000 Received: from [192.168.0.110] (a91-153-231-158.elisa-laajakaista.fi [91.153.231.158]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 3E2F3151602; Sun, 26 May 2013 10:28:37 +0300 (EEST) Message-ID: <51A1B9A4.4090701@iki.fi> Date: Sun, 26 May 2013 07:28:00 -0000 From: Tuomo Keskitalo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Patrick Alken CC: "gsl-discuss@sourceware.org" Subject: Re: new GSL version References: <519F8EAE.6010102@colorado.edu> In-Reply-To: <519F8EAE.6010102@colorado.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q2/txt/msg00011.txt.bz2 Patrick, publishing 1.16 would be great! Awesome if you can push it out. I don't know of any active development. BR, Tuomo On 05/24/2013 07:00 PM, Patrick Alken wrote: > Hi all, > > I think its time to make a new release of GSL (v1.16). There have > been a number of bugfixes and new features added in the last couple > years. I don't mind taking the lead on this but I was hoping to get a > little feedback from others on whether there are any critical > show-stopper bugs at the moment. > > Yesterday I removed 3 tests from specfun, poly, and cdf which were > causing 'make check' to fail on my system. I've created 3 separate bug > reports to track these issues on savannah. > > I admit I haven't been fully following all of the reported bugs, and I'm > sure there are plenty on bug-gsl that never made it into the bug > tracker. My thinking is that if there are no highly critical bugs at the > moment, we should go ahead with the new release, and then focus on bug > fixing for the following release. Many of the bugs in the tracker are > outside my area of expertise and will involve significant effort to > learn the algorithm to fix them, but I'm willing to spend some time in > the coming months to look into as many of them as I can. > > Also if any developers are current working on code they'd like to have > in the next release, let me know that too and we can hold off for a > little while. > > Patrick > -- Tuomo.Keskitalo@iki.fi http://iki.fi/tuomo.keskitalo