From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: jantien@xs4all.nl, fodber@interware.hu, guile-devel@gnu.org
Subject: Re: 1.8 time frame?
Date: Tue, 24 Aug 2004 16:30:53 +0200 [thread overview]
Message-ID: <lj1xhwhale.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <16674.26868.240712.580260@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Tue, 17 Aug 2004 22:22:12 +0200")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> I understand that you can't give a definite ETA, but is "closer"
> measured in weeks, months or quarter years?
Months.
> 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?
It is worse in the sense that it changes much more violently. But
since we try to be more backwards compatible now, there shouldn't be
much harm in doing this.
> I don't see the point of postponing releases.
You are probably right, we should make more visible releases of the
1.7 series. The snapshots are there, but you can't count them as
releases.
So, I will complete my string work (moving SRFI-14 into the core,
probably), and then make a 1.7.1 release.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-08-24 14:30 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
2004-08-17 21:16 ` Thamer Al-Harbash
2004-08-24 14:30 ` Marius Vollmer [this message]
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=lj1xhwhale.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--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).