X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 21 Jul 2015 20:19:15 -0400
Message-Id: <201507220019.t6M0JFHM030424@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <6D1A759F-0F14-4F04-8C20-AB0B8501AB63@noqsi.com> (message from
	John Doty on Tue, 21 Jul 2015 18:09:44 -0600)
Subject: Re: [geda-user] My gschem 1.9.1 is breaking rubber bands
References: <1437430095 DOT 1321 DOT 17 DOT camel AT ssalewski DOT de>	<alpine DOT DEB DOT 2 DOT 11 DOT 1507211410260 DOT 2035 AT nimbus>	<3B92001A-596F-4595-9DD3-15AAD3C3B1FF AT noqsi DOT com>	<1437494996 DOT 729 DOT 7 DOT camel AT ssalewski DOT de>	<0C548460-0355-4EFF-9495-75DE7AD13A16 AT noqsi DOT com> <CAOFvGD4ijprW7hoaJNYjo55A1=mnQuWCiK7Sku_WqC3NeUzgQw AT mail DOT gmail DOT com> <201507211821 DOT t6LILegK016798 AT envy DOT delorie DOT com> <55AE9814 DOT 4030702 AT ecosensory DOT com> <D24828BF-54B9-40A5-A51C-640EEAEC3D00 AT noqsi DOT com> <55AED575 DOT 9010702 AT ecosensory DOT com> <6D1A759F-0F14-4F04-8C20-AB0B8501AB63 AT noqsi DOT com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> But adding another feature is effectively doing nothing as far as
> most users are concerned, because we're not releasing the toolkit to
> packagers any more. Getting a 1.10 release out would *really* be
> doing something.

Are you volunteering to be the release manager?

Otherwise, the project does what the people doing the work are
interested in, and telling someone you think they're wrong won't (and
shouldn't) change anything.

Plus, telling someone that the work they want to do (likely for their
own benefit) is "effectively doing nothing" is very negative and
harmful.  Please don't do it again.

> And it's a bandaid, anyway. Rubberbanding *used* to work just
> fine. What added feature broke it?

You're assuming some added feature caused the problem.  It could have
been caused by an internal refactoring or some bugfix.  Perhaps you
could triage this a bit and see if the change was intentional or not?