public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gladman <brg@gladman.plus.com>
To: Patrick Alken <patrick.alken@Colorado.EDU>
Cc: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: new GSL version
Date: Fri, 24 May 2013 18:51:00 -0000	[thread overview]
Message-ID: <519FB66C.4060107@gladman.plus.com> (raw)
In-Reply-To: <519F8EAE.6010102@colorado.edu>

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

  reply	other threads:[~2013-05-24 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 16:00 Patrick Alken
2013-05-24 18:51 ` Brian Gladman [this message]
2013-05-24 20:50   ` Patrick Alken
2013-05-24 21:12     ` Brian Gladman
     [not found] ` <CAKDqugRByMUqy0s0r2trq=z3u3N4XkaCW=zANQ=MRDENB6dHig@mail.gmail.com>
2013-05-24 19:36   ` Patrick Alken
2013-05-26  7:28 ` Tuomo Keskitalo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=519FB66C.4060107@gladman.plus.com \
    --to=brg@gladman.plus.com \
    --cc=gsl-discuss@sourceware.org \
    --cc=patrick.alken@Colorado.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).