From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5087 invoked by alias); 24 May 2013 18:51:20 -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 5035 invoked by uid 89); 24 May 2013 18:51:13 -0000 X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BZ autolearn=ham version=3.3.1 Received: from avasout06.plus.net (HELO avasout06.plus.net) (212.159.14.18) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 24 May 2013 18:51:10 +0000 Received: from [192.168.1.4] ([212.159.26.30]) by avasout06 with smtp id fur51l0030eyEos01ur6Bh; Fri, 24 May 2013 19:51:07 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=dPWfxopb c=1 sm=1 tr=0 a=nO6JWm9Dsne7RoCvRGnC0w==:117 a=nO6JWm9Dsne7RoCvRGnC0w==:17 a=0Bzu9jTXAAAA:8 a=5uJ04jNixd4A:10 a=ihvODaAuJD4A:10 a=8nJEP1OIZ-IA:10 a=EBOSESyhAAAA:8 a=g7ztQKSZEvUA:10 a=jp3AaI8S0D7K7vhxSrwA:9 a=J1Xx371jFWi7YeLo:21 a=3pdRCAtwkXBZ-pMC:21 a=wPNLvfGTeEIA:10 X-AUTH: gladman+brg:2500 Message-ID: <519FB66C.4060107@gladman.plus.com> Date: Fri, 24 May 2013 18:51:00 -0000 From: Brian Gladman User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 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 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q2/txt/msg00005.txt.bz2 On 24/05/2013 17:00, 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. Hi Patrick I would certainly appreciate it if you are able to issue a new release as I cannot access the GSL repository at all. The problem is that I work on Windows where the current GSL repository is unusable because of its use of symlinks which the Windows versions of bzr do not implement. So attempts to use the repository just report errors. As a result this means that I have not been able to build or test any of the features that you and others have implemented since the last release. I should also add that I have reported and offered fixes for some bugs, at least one of which has not been acted on. Although I realise that Windows is not a priority for GSL, it would hardly make sense to leave bugs in place just because they have been discovered and fixed on Windows (in a fully portable way). I should also say that I am willing to help out on GSL if the bzr repository issue can be overcome in some way (there seems to be very is little prospect that the Windows issue will be fixed since, as far as I can tell, bzr development appears to have stopped). with my best regards, Brian Gladman