X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 12 Jul 2015 22:26:33 -0400
Message-Id: <201507130226.t6D2QXb6010971@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <55A229D3.3080501@zoot.drehmel.com> (message from Robert Drehmel
	on Sun, 12 Jul 2015 10:48:19 +0200)
Subject: Re: developer excitement? was Re: [geda-user] gEDA/gschem still alive?
References: <CAM2RGhTpfbqM7zNn72TBOjeL7B7LPT1PxSEU3+9aDdChFrPFTg AT mail DOT gmail DOT com>	<alpine DOT DEB DOT 2 DOT 00 DOT 1507090507530 DOT 6924 AT igor2priv>	<CAC4O8c_9mvUW6ub2EWCs2boucLdnzj5O_xCsaCNEaT17brLe0g AT mail DOT gmail DOT com>	<alpine DOT DEB DOT 2 DOT 00 DOT 1507091922140 DOT 6924 AT igor2priv> <CAC4O8c9jPo_wbpk2xnzGr6+Gdg0OFSBPyA-FYHjn_pE1PehZog AT mail DOT gmail DOT com> <55A229D3 DOT 3080501 AT zoot DOT drehmel 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


> Why not just create a centralized "experimental" branch where people can add
> their features, and more importantly, their clean-up and refactoring work in

I'm OK with doing that on the mainline, and using branches for
post-release stable updates.

And I'm certainly OK with people using branches on the main GIT for
their projects, which should make testing/merging easier.