Gnus development mailing list
 help / color / mirror / Atom feed
From: "Matt Armstrong" <matt+dated+1007585210.bd118d@lickey.com>
Cc: ding@gnus.org
Subject: Re: Oort releases
Date: Mon, 05 Nov 2001 13:46:47 -0700	[thread overview]
Message-ID: <87wv15aqtk.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <vxkr8rdyob1.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Mon, 05 Nov 2001 15:07:14 -0500")

Karl Kleinpaste <karl@charcoal.com> writes:

> Having commented a few moments ago about pGnus releases, it occurs to
> me that Oort is essentially never being updated.  That is, Oort has
> been in progress for...well, I'm not sure, but it's well over a year,
> and we've only gotten up to 0.04 so far.  I'll grant that Lars' former
> habits of releasing more than once a day at times was perhaps
> excessive, but shouldn't we get a consistent tarball out to folks a
> bit more regularly than we have up to this point?  oGnus 0.04 has been
> in existence for months, and there really are people who would like to
> use the under-development branch without cutting the soles of their
> feet on the bleeding edge of daily-CVS' potential hosage.
>
> If Oort isn't actually killing anybody off this week, could we hand
> users a new version, and move on to 0.05?

Yes, I think Gnus is experiencing symptoms of "Lars got a life"
syndrome.  It is not as bad as you might think -- the ChangeLog still
shows lots of stuff going on, but the dude who makes releases sure
hasn't been making as many, and I'm not clear on future milestones,
etc.  ;-)

-- 
matt



  reply	other threads:[~2001-11-05 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 20:07 Karl Kleinpaste
2001-11-05 20:46 ` Matt Armstrong [this message]
2001-11-05 21:43 ` Bill White
2001-11-06  8:39   ` Kai Großjohann
2001-11-06  9:39 ` Per Abrahamsen

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=87wv15aqtk.fsf@squeaker.lickey.com \
    --to=matt+dated+1007585210.bd118d@lickey.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).