From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: two oh, two oh, two oh
Date: Tue, 07 Dec 2010 11:19:48 +0100 [thread overview]
Message-ID: <m31v5tga0r.fsf@unquote.localdomain> (raw)
Hello!
We've sorta fallen off the 2.0 wagon in recent months. Much of it is my
fault, I think -- I needed a break, and set off to hack apps, and am
just coming back now.
And to be honest, Guile has seen a *lot* of features going in recently,
and this is a wonderful thing. Wonderful, but it does push back on the
2.0 schedule -- features have to be documented, they take hacktime, etc.
So we should be happy with the recent hacks, and happy to have a
breather before bearing down on 2.0. Which is what we should do now, I
think.
Let me propose a draft to-do list and schedule. All of the to-do items
are on top of our normal bugfixing and such. Please reply with
additions, comments, or changes.
* Blocker bugs for 2.0
- See if objcode space can be reserved for native code -- Andy / Noah
- The guile <-> unistring escaping issue -- ?
* Would-be-nice things for 2.0
- Merge in SoC work, finally (elisp, lua, peg parser) -- Andy
- Test ecmascript - ?
(For a long time it was broke at the REPL, due to a608cad27. Fixed
now, I think, but needs completion :/)
- Update website - ?
- "Marketing" plan - ?
* Schedule
- 15 Dec -- 1.9.14. I think we need another (!) prerel to consolidate
the changes since 1.9.13, and this will have been 2 months and
probably 150 commits.
- 15 Jan -- Branch for stable 2.0.x series, master becomes 2.1
- 1 Feb 2011 -- Release 2.0.0
I'm just pulling numbers and dates out of a hat here, but we need some
common milestones to focus on to finally birth this baby.
Thoughts, concerns, commentary?
Happy hacking,
Andy
--
http://wingolog.org/
next reply other threads:[~2010-12-07 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 10:19 Andy Wingo [this message]
2010-12-07 21:06 ` two oh, two oh, two oh Ludovic Courtès
2010-12-08 21:54 ` Neil Jerram
2011-01-27 10:46 ` Andy Wingo
2011-01-27 19:58 ` Ludovic Courtès
2011-01-28 14:21 ` Andy Wingo
2011-01-28 15:20 ` Ludovic Courtès
2011-01-28 20:09 ` Julian Graham
2011-01-29 11:10 ` Andy Wingo
2011-01-29 20:56 ` Ludovic Courtès
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=m31v5tga0r.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.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).