From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14094 invoked by alias); 24 May 2013 16:00:52 -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 14074 invoked by uid 89); 24 May 2013 16:00:49 -0000 X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_05,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from ipmx5.colorado.edu (HELO ipmx5.colorado.edu) (128.138.128.235) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 24 May 2013 16:00:48 +0000 From: Patrick Alken X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: An0FACSOn1GMrLMp/2dsb2JhbABZgwjDWhZtB4JiMw09EwMYAwIBAgFLDQgBAYgJmTiYRIgXkngDiR+UJ4s1gy4d Received: from bonanza.ngdc.noaa.gov ([140.172.179.41]) by smtp.colorado.edu with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 24 May 2013 10:00:47 -0600 Message-ID: <519F8EAE.6010102@colorado.edu> Date: Fri, 24 May 2013 16:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "gsl-discuss@sourceware.org" Subject: new GSL version Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q2/txt/msg00004.txt.bz2 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