public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Ed C. Lueless" <ed.c@lueless.org>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: Updated: cygwin-1.5.20-1
Date: Mon, 03 Jul 2006 15:14:00 -0000	[thread overview]
Message-ID: <20060703151418.GB28660@trixie.casa.cgf.cx> (raw)
In-Reply-To: <31DDB7BE4BF41D4888D41709C476B65704168C2B@NIHCESMLBX5.nih.gov>

On Mon, Jul 03, 2006 at 09:22:27AM -0400, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>Christopher Faylor wrote:
>> I've made a new version of the Cygwin DLL and associated utilities
>> available for download.  As usual, a list of what has changed is
>> below.  
>
>[snip]
>
>It's been over 6 hours since the last update.  When do you expect to
>have the next?

Good point.  It seems to me that if cygwin wants to survive and be
popular, we really need to use a continuous update model, just like
Linux and Solaris.

I'm not actually familiar with either of those two things but I do like
to make analogies whereever possible.  I'm fairly certain that both of
those OS's probably do releases on an hourly basis.  This is of great
benefit to the users because they have a *CHOICE* and, if a problem is
fixed, a user can benefit immediately.  With Cygwin, we sometimes have
to wait YEARS for an update which fixes a problem.  I don't see how that
benefits anyone.  Wouldn't you think that the developers would want
their fixes actually used and tested?

And, yes, I know about snapshots.  I don't use them because they're
unstable and require manual steps to install.  I did try a snapshot last
year, and had to spend the rest of the day recovering from it!

Btw, I used to use a system which released on a 15-minute basis but I
don't expect anyone to go to those lengths.  This is OSS after all! I
know that it is all volunteer!
--
Ed C. Lueless                    Computer Geru/Master Programmer
"There's no such thing as evil.  Just excuses that heaven won't accept." -- Peter David
"Ed C.  - you are the man!" -- my boss

  reply	other threads:[~2006-07-03 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060702161616.GA10851@coe.casa.cgf.cx>
2006-07-03 13:22 ` Buchbinder, Barry (NIH/NIAID) [E]
2006-07-03 15:14   ` Ed C. Lueless [this message]
2006-07-03 16:30   ` Igor Peshansky

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=20060703151418.GB28660@trixie.casa.cgf.cx \
    --to=ed.c@lueless.org \
    --cc=cygwin-talk@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).