From owner-freebsd-current@FreeBSD.ORG Fri Nov 11 18:33:13 2011 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 395A6106564A for ; Fri, 11 Nov 2011 18:33:13 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id E92838FC14 for ; Fri, 11 Nov 2011 18:33:12 +0000 (UTC) Received: by qabj40 with SMTP id j40so4481069qab.13 for ; Fri, 11 Nov 2011 10:33:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ppKw4WcLsyMO7kpaFNEJvD6qesfr10GsJnB62gWx9OU=; b=F/LZCe8kia0vxItIcUfgq2t776acQyWXHamXqVTgjW27K+r/dGdPjW5RP2t3MWWkkA Q2CnHiwNaZdl08V8En804rqsgH3DY+nBgQeZHg3PuG5RjAmrAe89JKCtdcsWXmFzFqev LHPt6XNbu1aGOJzOYL3m53BQH4Oructk3iby4= MIME-Version: 1.0 Received: by 10.224.185.199 with SMTP id cp7mr9949100qab.68.1321036392012; Fri, 11 Nov 2011 10:33:12 -0800 (PST) Received: by 10.224.73.195 with HTTP; Fri, 11 Nov 2011 10:33:11 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Nov 2011 13:33:11 -0500 Message-ID: From: Mehmet Erol Sanliturk To: Benjamin Kaduk Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current Subject: Re: Use of newest version number such as 10.0 instead of current 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: Fri, 11 Nov 2011 18:33:13 -0000 On Fri, Nov 11, 2011 at 12:29 PM, Benjamin Kaduk wrote: > On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote: > > Dear all , >> >> Instead of using Current and then renaming everything for a new version >> number , >> is it not possible to use the newest version number in place of Current >> when it is branched . >> >> Such a change will prevent unnecessary renaming problems . >> >> >> For everyone , it i very easy to understand that 10.0 is the latest , >> therefore the current one . >> >> The current may be used as a symbolic link to the newest version number , >> such as used by Debian . >> >> >> For example , for FreeBSD 9.0 RC1 , the ports directory name was >> >> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current/Latest/ >> >> >> which is NOT available now , and >> >> >> pkg_add -r * >> >> is giving error about directory not found . >> >> >> This is preventing testing and / or using efforts . >> >> >> I know , it is possible to rename local link names , but >> everyone is not so much knowledgeable . >> > > I'm not sure I understand your proposal. > In a month (er, two. well, maybe three) when 9.0 is released, do you > propose that the svn HEAD be called: > (a) 10.0 > (b) 9-CURRENT > (c) CURRENT > (d) something else > > I do not realy care for either (a) or (b), since (a) would imply that the > version is not changing, even as incompatible KBI/ABI changes are made. > Likewise for (b), once the KBI/ABI changes, HEAD is decidedly no longer a > form of '9'. > > -Ben Kaduk > During development of Version 9 , the name of directory was ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current/Latest/ During the 9.0 Release RC1 , the above name was used . Before releasing the 9.0 Release RC2 , the above has been changed . This change has broke the links in 9.0 Release RC1 . When we look at the ftp sites ( including mirrors ) all of them has changed . This naming structure is requiring re-structuring all of the directories over all ftp , and other sites . This is a wasted effort . Instead of doing this , a scheme like the following may be used : Instead of using /*-9-Current/ , use 10.0 for current . Assume our main directory is the following : ftp://ftp.freebsd.org/pub/FreeBSD/ As next directory , use 8.1 , 8.2 , 9.0 for current . ftp://ftp.freebsd.org/pub/FreeBSD/8.1/ ftp://ftp.freebsd.org/pub/FreeBSD/8.2/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/ All of the directories , for example , ... ports ... release ... snapshot ... whatever is related to 8.2 , 9.0 will be under 8.2 or 9.0 , in such a way that nowhere else a directory with name , for example , 9.0 will exist ... For example : ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/ports/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/packages/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/snapshot/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/release/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/stable/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/doc/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/doc/handbook/ ftp://ftp.freebsd.org/pub/FreeBSD/9.0/amd64/doc/man/ .... Explain to the people that 9.0 is the "Development" branch , NOT for production use . A single sentence to learn . Another step may be to insert an explicit warning message into current motd file about "Development" status of 9.0 . When time comes to make a release of 9.0 , which a new development branch will be generated , take a copy of 9.0 , and rename this directory as 10.0 . By using suitable find/replace scripts , find all occurrences of 9.0 with strict match and replace them by 10.0 . After generating directory 10.0 , propagate it to mirrors . Please , notice that , NOTHING is changed for the 9.0 , and NOTHING is broken with respect to generation of a new branch , all over the world .... Then start to work on 10.0 ... Continue in that way . Apply the similar steps to 9.0 for 9.1 : Take a copy of 9.0 , rename it as 9.1 , ... Thank you very much . Mehmet Erol Sanliturk