X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Fri, 16 Dec 2011 13:46:23 -0500
Message-Id: <201112161846.pBGIkNfG021985@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20111216183708.GA30970@malakian.lan> (message from Andrew
	Poelstra on Fri, 16 Dec 2011 10:37:09 -0800)
Subject: Re: [geda-user] PCB sync request for the upcoming Ubuntu long term
 support release
References: <CAHu0Z0WqAUZrADSxwywEzi6+KsA5+=hTfgWd7yJWYyxMYaWpHg AT mail DOT gmail DOT com> <20111216183708 DOT GA30970 AT malakian DOT lan>
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


> What needs to be done before we can do a fresh bugfix release of
> pcb? Is it just that somebody with permissions needs to take the
> time, or are there pending showstoppers that need dealing with?

Some needs to review the open bugs and tag those that should be in
this bug release.

Then we fix those, then release.

My goals for this release are to make pcb solid enough on all
platforms that we can take the time to re-engineer the internals,
which is likely to make pcb "broken" for a while.