X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9yYSKN8Wx5SSilNgeKT6Aj7LiL6d1CQR8Um4TyreGis=; b=MGq71ws7ZRkgFszmekW+qvoD8bS6zRQ6HnLdEASuOke6NVN0vHK1nqAyGjWTbDrVrt CK7LWrtOOc79n/wbn7QVdUvayp5DnAJurmXtvd116NzVNPgjLcxUfidcC7wLzFqJUKtk SLcHXF2sQEN55zCc5bvklbnUIP2lTsOliMlQzC6NSYGAJcc7gee5JJKCZVmTg++UEkAI QtUn3mQiceIeVs5zETBlRBLQEBt4ubhvv39dlLYjtlNHFbvPBE3jslEUonNAbTFDbNFZ upQW1jMn9VVj5nBJAqdaii2oQi2s/PUoxjqHnPC66YvV9sXCuAIFa4xOz8xYkZBpGcYP UMTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=9yYSKN8Wx5SSilNgeKT6Aj7LiL6d1CQR8Um4TyreGis=; b=XHwWMTlYTyVAzQtEhtiYCjjX+14hUdtq2HSc1kvg1OC7EaGXNP85sqs3Tvyq+6rL7p RpfwsbIznImGVeZ5qbK99GEPPuKJp5dNvMOjtHNz/Tc3LC3Fi4EkYb0IMvxrW4n6Okua yMXBkwcdc0OOUoiyw89jOXCIOkGrEXBIDwHvu4CYDQqnkhobHPjPft3MLoK3RJ3SAzcs IGLPxg4OlHF30MTgh6Pk4rEMNz0eEcRTQzahMqTQIGjuWNyHNd9OinNddiwB1bhZFkWQ YLIbkUhLvyTbM4QzFcULcMdeAebGJh8dyyn6u7gyWVY+4ICqj6Ynk1VvD+SNp0y3DPQ/ XX1Q== X-Gm-Message-State: AG10YOTq2VYgtNfUoGhrMgb+vK5rUc16NADlvsvdYY99yXb1kuhnzxZcgYBlRNdSN8plEr8LI/rbuOotjqjGwg== MIME-Version: 1.0 X-Received: by 10.28.125.147 with SMTP id y141mr11698653wmc.18.1453407281521; Thu, 21 Jan 2016 12:14:41 -0800 (PST) In-Reply-To: <20160121000930.e02a8a54b74efb839db9f7bd@gmail.com> References: <20151223195846 DOT 8392 DOT qmail AT stuge DOT se> <20151229155647 DOT GA3752 AT localhost DOT localdomain> <20151229175222 DOT GD3752 AT localhost DOT localdomain> <96A12FC1-E09C-4D63-8346-5A62FDAB4228 AT sbcglobal DOT net> <20160120173024 DOT GB16858 AT localhost DOT localdomain> <201601201903 DOT u0KJ3Lx4026878 AT envy DOT delorie DOT com> <20160120210035 DOT 3859 DOT qmail AT stuge DOT se> <20160121000930 DOT e02a8a54b74efb839db9f7bd AT gmail DOT com> Date: Thu, 21 Jan 2016 11:14:41 -0900 Message-ID: Subject: Re: [geda-user] Releaseability of gEDA code From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a11419974bab14e0529ddc094 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 --001a11419974bab14e0529ddc094 Content-Type: text/plain; charset=UTF-8 On Wed, Jan 20, 2016 at 2:09 PM, Nicklas Karlsson ( nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] < geda-user AT delorie DOT com> wrote: > > On Wed, Jan 20, 2016 at 12:00 PM, Peter Stuge (peter AT stuge DOT se) [via > > geda-user AT delorie DOT com] wrote: > > > > > DJ Delorie wrote: > > > > Do we want to change how we do development? > > > > > > For the sake of simplicity I am a strong proponent of having master > > > be releaseable at all times. > > > > > > > Then we need another branch unstable_master or something, because what > you > > propose means in practice that we aren't going to test each other's work > > much before unleashing it on unsuspecting users. Are you really likely > to > > go through and carefully try every branch? > > I think there should be a head/master branch there everything enter as > soon as possible. > > Then there would be a need to fork of "stable" releases, preferably only > disable features which do not work well because time spent on release will > to at least some extent be lost from development. > You just don't merge things that cause lots of problems into release_master. This way getting into unstable_master isn't a free pass: if it annoys everyone getting into release is obviously going to get resistance. But you can still develop off recent work without having to constantly juggle things between branches. Britton --001a11419974bab14e0529ddc094 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jan 20, 2016 at 2:09 PM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-use= r AT delorie DOT com> wrote:
> On Wed, Jan 20, 2016 at 12:00 PM, Peter Stuge (peter AT stuge DOT se) [via
> geda-user AT delorie DOT com] &l= t;geda-user AT delorie DOT com> wr= ote:
>
> > DJ Delorie wrote:
> > > Do we want to change how we do development?
> >
> > For the sake of simplicity I am a strong proponent of having mast= er
> > be releaseable at all times.
> >
>
> Then we need another branch unstable_master or something, because what= you
> propose means in practice that we aren't going to test each other&= #39;s work
> much before unleashing it on unsuspecting users.=C2=A0 =C2=A0Are you r= eally likely to
> go through and carefully try every branch?

I think there should be a head/master branch there everything enter = as soon as possible.

Then there would be a need to fork of "stable" releases, preferab= ly only disable features which do not work well because time spent on relea= se will to at least some extent be lost from development.
<= div>
You just don't merge things that cause lo= ts of problems into release_master.=C2=A0 This way getting into unstable_ma= ster isn't a free pass: if it annoys everyone getting into release is o= bviously going to get resistance.=C2=A0 But you can still develop off recen= t work without having to constantly juggle things between branches.
=C2=A0
Britton

--001a11419974bab14e0529ddc094--