public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Patrick Alken <patrick.alken@Colorado.EDU>
To: gsl-discuss@sourceware.org
Subject: Re: Next Version?
Date: Thu, 19 Jun 2014 20:08:00 -0000	[thread overview]
Message-ID: <53A34339.7070608@colorado.edu> (raw)
In-Reply-To: <02E5613E-E5F7-4225-B8A9-11D71EEFD09E@phas.ubc.ca>

On 06/19/2014 07:58 PM, Jean-François Caron wrote:
> Hello, I am wondering if anyone has an update on when we might see the next version of GSL?  Is it something like “in the next month”, “by the end of summer”, or “next year”?  
> 
> I donÂ’t need any details, IÂ’m just being impatient because my contribution is supposed to appear in the next version, and I wish to make a patch for CERNÂ’s ROOT that will use the new feature.  So just a short answer will be enough to satisfy me.  = )
> 
> Jean-François
> 

I've been completely swamped lately. The lapack/flame issue is still
unresolved - I don't mind pushing this off to 3.0 in order to get 2.0
out more quickly. Gerard is working on a new memory management scheme
which may take a while to complete - perhaps he would agree to wait
until 3.0 to include that?

I think those are the two main issues to resolve. If we can agree to
postpone these features until 3.0, then 2.0 could be released fairly
quickly...maybe within a month or two, though Rhys may have some other
things in mind to work on.

Patrick

  parent reply	other threads:[~2014-06-19 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 17:59 Jean-François Caron
2014-06-19 18:01 ` Rhys Ulerich
2014-06-19 20:08 ` Patrick Alken [this message]
2014-06-20  0:06   ` Gerard Jungman
2014-06-19 20:09 ` Patrick Alken
2014-06-19 20:13   ` Jean-François Caron
2014-06-26 20:11 ` Patrick Alken

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=53A34339.7070608@colorado.edu \
    --to=patrick.alken@colorado.edu \
    --cc=gsl-discuss@sourceware.org \
    /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).