From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: Schedule proposal for the next release(s)
Date: Wed, 05 Jul 2006 23:22:00 -0000 [thread overview]
Message-ID: <17580.18778.749722.831674@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060705224744.GF678@adacore.com>
> > If this is agreed I think it should be added to:
> >
> > http://sourceware.org/gdb/schedule/
> >
> > which is already out of date.
>
> Page updated.
Thanks. I think the release schedule is a good idea is it gives developers an
expectation and they can plan accordingly. With Emacs there is no schedule. :-(
On the release history, the only things I find interesting are the number and
the actual release date. It might also be a good idea to link to the NEWS
file (not to be confused with the current link to News). Slippage makes me
think of performance reviews where the manager wants to know why the release
was late but does not appreciate the quality of the release.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2006-07-05 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 8:11 Joel Brobecker
2006-06-24 2:26 ` Nick Roberts
2006-06-24 7:40 ` Joel Brobecker
2006-07-05 22:47 ` Joel Brobecker
2006-07-05 23:22 ` Nick Roberts [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17580.18778.749722.831674@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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