From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:20:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3330216A41B for ; Wed, 10 Oct 2007 14:20:16 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx3.netclusive.de (mx3.netclusive.de [89.110.132.133]) by mx1.freebsd.org (Postfix) with ESMTP id C4AB113C447 for ; Wed, 10 Oct 2007 14:20:15 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdc93.f.ppp-pool.de [195.4.220.147]) (Authenticated sender: ncf1534p2) by mx3.netclusive.de (Postfix) with ESMTP id D97D8604C1C for ; Wed, 10 Oct 2007 15:59:39 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id 98C7F15217; Wed, 10 Oct 2007 15:52:14 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Wed, 10 Oct 2007 15:52:14 +0200 (CEST) Organization: Convenimus Projekt Lines: 58 Message-ID: NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192024334 88189 192.168.100.5 (10 Oct 2007 13:52:14 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Wed, 10 Oct 2007 13:52:14 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: suggest renaming and extending the -CURRENT and -STABLE lines X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2007 14:20:16 -0000 Hello people! Before you all bang around on my head :-) hear me out on this one. It's actually possible that someone has already made this suggestion and I haven't found that thread yet. If so, please point me in the right direction and I'll read up on it, before writing in this thread again. In computer science and mathematics, we sometimes use terms from the "normal" language but use them just a little differently than people outside of our circle would. Sometimes that is unavoidable because our language is just doesn't have enough words to express our thoughts - and to express them exactly. This is usually not much of a problem. However, sometimes we have to communicate with others, who may use our products and ideas but don't embrace our language. As the subject of this thread already suggests, I am referring to the names of the developement branches, which I (even as a computer scientist) consider a little "strange". If someone sees the result of RELENG_6 is called STABLE, he or she will problably think, this is the line where bug fixes are added, security problems fixed and the whole thing is meant for production systems. While the first two things may be true, I would not suggest RELENG_6 for production systems. Normally the -STABLE line works fine. But I *have* times in the past where a driver was changes and suddenly the system *didn't* work after a reboot or showed strange behaviour. What you could (and should?) use for a production system is RELENG_6_2. I am using that, as you can see in the header. :-) Although the handbook titles RELENG_6 as "staying stable...", people are warned not to use it on production systems (which seems strange for something called "stable") while RELENG_6_x isn't even mentioned. What I propose is this: When we have FreeBSD 7.0-RELEASE, we change these things a little. - What is -CURRENT now stays -CURRENT (then probably 8-CURRENT). - RELENG_7 is also called -CURRENT (7.x-CURRENT) - RELENG_7_x could be called 7.x-RELEASE-px (see below) Additionally, I suggest adding a new target. What we numbers we put at the end of the RELENG_ isn't too important at the moment. This would be the new -STABLE brach - and would deserve the name. It would point to the current release and the newest patch. So basicly, if I started at 6.2-RELEASE, it would have brought me through all the patches of that release and will update to 6.2-RELEASE once that is out and so on. I realize that this is somewhat of a change and also that progress is always frowned upon. :-) But IMHO it is a step in the right direction into the right direction because it removes a word that can easily be misunderstood - even by a user who isn't a complete beginner. I'd like your thoughts about this and maybe we can work something out that isn't exactly my idea but will work for the public. Regards Chris