Re: Use of newest version number such as 10.0 instead of current

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