From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: linux-audio-dev@music.columbia.edu, alsa-devel@lists.sourceforge.net
Subject: Re: [linux-audio-dev] Re: ALSA homepage redesign
Date: Thu, 18 Apr 2002 20:28:59 +0100 [thread overview]
Message-ID: <3CBF1E7B.9000700@superbug.demon.co.uk> (raw)
In-Reply-To: 3CBEF1EB.3EE856B3@folkwang-hochschule.de
Joern Nettingsmeier wrote:
>James Courtier-Dutton wrote:
>
>
><...>
>
>
>>I think we should have a section on the web site for the different
>>applications which support different alsa versions.
>>
>>
>>
>
>NOOOO. could we please please please annihilate every last little
>trace of alsa 0.5.x from that page ?
>if that's the stable release, people should be using kernel 1.2 on
>an 8086 (as everyone knows, that's the stable release of the
>pentium).
>
>if it has to be, add a very small link to *OBSOLETE* releases and
>apps that use them, but please not on the front page. i don't know
>how often i have told newbies who had just freshly installed
>"stable" to ditch it and start over with 0.9...
>
>i don't see why jaroslav has sticked to this stable/unstable naming
>scheme so long, but probably he had too many other things to do.
>patrick, please fix this asap.
>
>set_rant_mode(off);
>
>really like the new site. good to see it maintained, and the three
>main links for different interest groups are an excellent idea.
>
>jrn
>
>
>
I agree with you. The web site currently only mentions applications
compatible with alsa 0.5.x
There is no mention of 0.9.x at all in the applications section.
If alsa follows ISO9000 release numbering guidelines, the full, non beta
release should be called 0.10.x
Apparently you should not have beta 0.9.x and then go to full release
0.9.x, apparently one should go to 0.10.x for the first non-beta
release, and then only have bug fixes updating 0.10.x. Maybe that is why
the linux kernel follows this pattern. Developement 2.3.x, release
2.4.x, development 2.5.x, release 2.6.x
Cheers
James
next prev parent reply other threads:[~2002-04-18 19:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 6:00 ALSA homepage redesign Patrick Shirkey
2002-04-18 7:34 ` Maarten de Boer
2002-04-18 12:41 ` Andy Wingo
2002-04-18 13:11 ` Eric Dantan Rzewnicki
2002-04-18 13:22 ` James Courtier-Dutton
2002-04-18 16:18 ` [linux-audio-dev] " Joern Nettingsmeier
2002-04-18 17:17 ` Juan Linietsky
2002-04-18 17:27 ` Fred Gleason
2002-04-18 17:43 ` James Tappin
2002-04-18 18:52 ` Fred Gleason
2002-04-18 19:32 ` Thierry Vignaud
2002-04-19 9:02 ` Takashi Iwai
2002-04-18 19:28 ` James Courtier-Dutton [this message]
2002-04-18 22:25 ` Bob Colwell
2002-04-18 16:29 ` joy ping
2002-04-18 20:30 ` [linux-audio-dev] " Josh Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CBF1E7B.9000700@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-audio-dev@music.columbia.edu \
--cc=nettings@folkwang-hochschule.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.