www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/09/15/08:13:38

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Tue, 15 Sep 2015 14:17:23 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Happy birthday
In-Reply-To: <20150915115059.5939.qmail@stuge.se>
Message-ID: <alpine.DEB.2.00.1509151410560.6924@igor2priv>
References: <55F7EE7F DOT 101 AT unige DOT ch> <20150915115059 DOT 5939 DOT qmail AT stuge DOT se>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
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


On Tue, 15 Sep 2015, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote:

> Juergen Harms (juergen DOT harms AT unige DOT ch) [via geda-user AT delorie DOT com] wrote:
>> distributions have the policy of strictly limiting the distributed
>> software to stable versions of upstream packages.
>
> Yes, it's really sad that distributions offer so little added value.
> There is a huge potential for distribution differentiation in
> following upstreams much more closely. Oh well.

I wouldn't blame distributions. As a plain user, I wouldn't know when to 
use a current git version either. Is there a place where developers 
announce that a specific VCS version is stable, or how do I know it's not 
some WIP/experimental stuff at the moment I pull? Or is it guaranteed 
(more or less) that a specific branch is always stable after each 
push/merge/whatever? And then how often should I look and try the new 
version? Should the distribution's package manager upload 15 new packages 
a day if the upstream VCS changed 15 times that day?

Releases can solve this: when upstream rolls a new release, at least the 
developers/maintainers of the upstream think that version of the stuff is 
stable. This is a signal from upstream to users and distributions.

Regards,

Igor2

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019