public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: rcunningham@ucsd.edu
To: cygwin-xfree@cygwin.com
Subject: Re: run.exe will not work with upgrade from 1.14.4 to 1.16.3
Date: Sat, 03 Jan 2015 09:25:00 -0000	[thread overview]
Message-ID: <83E13E19-3E7A-446B-82DB-A331A2F84D43@ucsd.edu> (raw)
In-Reply-To: <54A7A26E.7090801@blankersfamily.com>



On January 3, 2015 12:03:58 AM PST, Laurens Blankers <laurens@blankersfamily.com> wrote:
>I am not arguing that the solution should be discarded, I am arguing
>that the way the transition was handled, or not handled actually, it
>not
>worthy of being called engineering, development, or even programming.

Strong words, but absolutely correct.

Transitions affecting the user experience should be gradual, not violent.

This was an unnecessarily violent transition with much breakage.

Revert, replan, redeploy.

-BobC


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2015-01-03  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 20:11 schilpfamily
2015-01-02 20:21 ` Laurens Blankers
2015-01-02 20:35   ` schilpfamily
2015-01-03  3:49     ` Larry Hall (Cygwin-X)
2015-01-03  8:04       ` Laurens Blankers
2015-01-03  9:25         ` rcunningham [this message]
2015-01-03 23:02         ` Larry Hall (Cygwin-X)
2015-01-04 11:41           ` Laurens Blankers
2015-01-05  4:04             ` Larry Hall (Cygwin-X)
2015-01-05  9:07               ` Laurens Blankers
2015-01-05  9:49                 ` Yaakov Selkowitz
2015-01-05 10:03                   ` Laurens Blankers
2015-01-05 10:34                     ` Yaakov Selkowitz
2015-01-06  4:19                 ` Larry Hall (Cygwin-X)
2015-01-12  0:26   ` solution for package startup scripts changing: do your own (was Re: run.exe will not work with upgrade from 1.14.4 to 1.16.3) Linda Walsh

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=83E13E19-3E7A-446B-82DB-A331A2F84D43@ucsd.edu \
    --to=rcunningham@ucsd.edu \
    --cc=cygwin-xfree@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).