Re: A new Gnus 5.10 release...

[gdt@work.lexort.com]

  Unless people think that (a)-(d) _must_ be added to v5-10 _before_ the
  release, I'd suggest to do another release quite soon after (a)-(d)
  have been merged into v5-10.  At the same time we might get more
  feedback and bug reports from people who didn't use any non-released
  version (i.e. anything newer than 5.10.6) yet, i.e. I expect that
  these won't be the only changes.

(I'm new to the list, and just started using gnus with nnimap for mail
- I'm a longtime gnus user for reading mailinglists from mh folders.)

When I started using nnimap I had trouble (with the code in emacs
21.3), and went to find more updated code, and wondered if gnus was
dead given the release dates and the apparent broken gatewaying to
news://news.gnus.org/gnus.ding I quickly figured out that CVS is where
one should go.

I think having a stable release - without trying to make changes just
before the release is a good idea.  There's a big tendency, quite
understandable, to push features in just before a stable release, but
I think this should be avoided as not conducive to stability.

Once a stable release is out, merging stuff (that might cause trouble)
and having another release in a month or so would get those features
out, and not jeopardize the stability of the just-about-to-happen
stable release.

-- 
	Greg Troxel <gdt@work.lexort.com>