X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-ASG-Debug-ID:	1453324581-0aa85229201cbfd0001-9re8WH
X-Barracuda-Envelope-From:	gheskett AT shentel DOT net
X-Barracuda-RBL-Trusted-Forwarder:	204.111.2.17
From:	"Gene Heskett (gheskett AT shentel DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Barracuda-Effective-Source-IP:	n64s149.fttx.shentel.net[204.111.64.149]
X-Barracuda-Apparent-Source-IP:	204.111.64.149
X-Barracuda-RBL-IP:	204.111.64.149
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Project leadership
Date:	Wed, 20 Jan 2016 16:16:20 -0500
X-ASG-Orig-Subj:	Re: [geda-user] Project leadership
User-Agent:	KMail/1.9.10 (enterprise35 0.20100827.1168748)
References:	<20151222193859 DOT 26898 DOT qmail AT stuge DOT se> <20160120173024 DOT GB16858 AT localhost DOT localdomain> <201601201903 DOT u0KJ3Lx4026878 AT envy DOT delorie DOT com>
In-Reply-To:	<201601201903.u0KJ3Lx4026878@envy.delorie.com>
X-KMail-QuotePrefix:	>
MIME-Version:	1.0
Message-Id:	<201601201616.20434.gheskett@shentel.net>
X-Barracuda-Connect:	smtp1.edbg.cloud.shentel.net[204.111.2.17]
X-Barracuda-Start-Time:	1453324581
X-Barracuda-URL:	https://barracuda1.shentel.net:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size:	1952
X-Virus-Scanned:	by bsmtpd at cloud.shentel.net
X-Barracuda-BRTS-Status:	1
X-Barracuda-BRTS-Evidence:	geneslinuxbox.net
X-Barracuda-Spam-Score:	0.50
X-Barracuda-Spam-Status:	No, SCORE=0.50 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=WEIRD_PORT
X-Barracuda-Spam-Report:	Code version 3.2, rules version 3.2.3.26304
	Rule breakdown below
	pts rule name description
	---- ---------------------- --------------------------------------------------
	0.50 WEIRD_PORT URI: Uses non-standard port number for HTTP
Reply-To:	geda-user AT delorie DOT com

On Wednesday 20 January 2016 14:03:21 DJ Delorie wrote:

> > and we should allow a new release at any time.
>
> We usually run in phases - during development we're not "release
> ready" but then we switch to release mode to stabilize and clean up
> master.  Many project run in cycles like this.  Do we want to change
> how we do development?  IMHO wherever the most development is
> happening, is both going to be a bit unstable and going to be where
> all the stuff you want to release is.
>
> On the PCB side we create a branch for each release, and those
> branches must always be "release ready" just in case, but not master.
> Master is where things come together, so we have to allow for some
> chaos.

I may have found my missing holes, it appears the gcode exporter was also 
creating a separate file for each hole that was smaller than the tool 
size I had given it in the export's fill in the blanks menu.  The size 
of thed drill tool I had spec'ed at 0.03125", and it seems to have 
output a file for the 0.028" holes, and a file for the 0.020 diameter 
holes. But while I did check, my box of smaller tools smallest tool was 
the 0.03125 mill.  I could I suppose order a  box of 0.020" mills, but I 
have no clue if they would be strong enough to bore a hole 0.0425" in 
diamater with tha same alacrity it did with the much stronger 0.03125" 
mill.  I think that would be much more to the liking if the spindle ran 
10x faster. That kit in on a truck, but it will be fun to mount as I 
bought an air cooled motor and its 80mm in diameter. Thats 
3.14960629921259843".  And an additional 3 lbs for the z motor to lift.  
S/B fun to mount, and get it trammed to the rest of the Z head.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

- Raw text -