From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: jantien@xs4all.nl, fodber@interware.hu, guile-devel@gnu.org
Subject: Re: 1.8 time frame?
Date: Tue, 17 Aug 2004 22:22:12 +0200 [thread overview]
Message-ID: <16674.26868.240712.580260@byrd.xs4all.nl> (raw)
In-Reply-To: <87y8kgb7pu.fsf@zagadka.ping.de>
mvo@zagadka.de writes:
> > What's the latest update on the status of the guile 1.8 release plan?
>
> It is getting closer, it's hard to say when it will arrive. I'm
> working full-time on the new C API for data type conversions, and I
> hope that I have strings and symbols nailed next week. The rest
> should be simpler...
I understand that you can't give a definite ETA, but is "closer"
measured in weeks, months or quarter years? I have a very nasty
heisenbug here, and I would rather not debug it, if possible.
> > Have you considered moving to a regular release schedule (like the
> > GNOME project does?).
>
> Hmm, my feeling is that this will not work very well with Guile since
> Guile is a much smaller project with fewer people working on it.
In any case I would welcome this very much. Most of my contributions
were due to LilyPond. I find it very frustrating to wait for years for
my changes to show up. I prefer released software with some rough
edges to perfect software which is not released at all. Surely current
CVS is better in all regards than the 1.6 release? I don't see the
point of postponing releases.
Anyway, my 2 cents.
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-17 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 16:03 1.8 time frame? Han-Wen Nienhuys
2004-08-15 18:02 ` Marius Vollmer
2004-08-16 20:02 ` Andy Wingo
2004-08-17 20:22 ` Han-Wen Nienhuys [this message]
2004-08-17 21:16 ` Thamer Al-Harbash
2004-08-24 14:30 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16674.26868.240712.580260@byrd.xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=fodber@interware.hu \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).