From owner-freebsd-multimedia@FreeBSD.ORG Tue Jun 30 13:11:51 2009 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B037E1065688 for ; Tue, 30 Jun 2009 13:11:51 +0000 (UTC) (envelope-from Joerg.Schilling9ab33xy531fokus.fraunhofer.de@bounce.antispameurope.com) Received: from relay01-haj2.antispameurope.com (relay01-haj2.antispameurope.com [83.246.65.51]) by mx1.freebsd.org (Postfix) with ESMTP id 39DE58FC20 for ; Tue, 30 Jun 2009 13:11:50 +0000 (UTC) (envelope-from Joerg.Schilling9ab33xy531fokus.fraunhofer.de@bounce.antispameurope.com) Received: by relay01-haj2.antispameurope.com (ASE-Secure-MTA, from userid 1000) id DD31A9418B; Tue, 30 Jun 2009 15:11:48 +0200 (CEST) Received: from pluto.fokus.fraunhofer.de (pluto.fokus.fraunhofer.de [195.37.77.164]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by relay01-haj2.antispameurope.com (ASE-Secure-MTA) with ESMTP id 3DE49940FE; Tue, 30 Jun 2009 15:11:48 +0200 (CEST) Received: from EXCHSRV.fokus.fraunhofer.de (bohr.fokus.fraunhofer.de [10.147.9.231]) by pluto.fokus.fraunhofer.de (8.14.2/8.14.2) with SMTP id n5UDBmte005410; Tue, 30 Jun 2009 15:11:48 +0200 (MEST) Received: from rigel ([10.147.65.195]) by EXCHSRV.fokus.fraunhofer.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 30 Jun 2009 15:11:48 +0200 Date: Tue, 30 Jun 2009 15:11:48 +0200 From: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling) To: avg@icyb.net.ua Message-ID: <4a4a0f14.ylvYB6h9MqEdvjIP%Joerg.Schilling@fokus.fraunhofer.de> References: <4a487b0b.il/42Wi7dzHBxk4X%Joerg.Schilling@fokus.fraunhofer.de> <4A4A03C3.6070903@icyb.net.ua> <4a4a05f5.7bXPwuzCTABxJvS6%Joerg.Schilling@fokus.fraunhofer.de> <4A4A084B.2050405@icyb.net.ua> In-Reply-To: <4A4A084B.2050405@icyb.net.ua> User-Agent: nail 11.22 3/20/05 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Jun 2009 13:11:48.0375 (UTC) FILETIME=[5334FA70:01C9F984] Cc: freebsd-multimedia@freebsd.org, dfpleal@gmail.com Subject: Re: cant burn a cd iso X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 13:11:52 -0000 Andriy Gapon wrote: > > What is the reason for following the "Old/Stable" link? > > > > 2.01 is completely outdated and should be avoided because of many bugs (e.g. in > > mkisofs). > > Sorry if sounded like a smart-ass, I didn't intend that. > I had suspicions about "Old" part of the link, but I was looking for "Stable". "stable" means dead and "will not change". > Maybe we just see different things behind words like "alpha", "beta" and "stable". > But FreeBSD ports typically track stable releases of third-party programs, only in > exceptional cases we create "-devel" versions of the ports that track betas or > other kind of WIP. There is "pre-alpha" which may happen under special conditions, e.g. after a bigger change was introduced. There is no real difference between alpha and beta. "stable" as alias for "dead" was already mentioned. Decent software development always tries to be 100% bug free. In a decent software development, interface changes (if needed at all) are announced many years before they are implemented. For this reason, people only should get into problems if they ignore announced changed for more than 3-5 years. > I realize that there is a new trend of "permanently beta" software (GOOG), but I > think that it would be beneficial to the community of users of your software if > you'd split Old and Stable categories and declared some recent version of cdrtools > to be a Stable Release. There seems to be a general trend towards longer so called "development cycles". Sun did e.g. publish Solaris 10 in February 2005 and there is still no Solaris 11. The OpenSource development is a smoothly moving target and you cannot synchronize different projects anyway. If you follow the rule to always publish bug-free versions if possible, people can live with this paradigm.