Message-Id: <199512201836.KAA06254@rah.star-gate.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Jim Lowe <james@miller.cs.uwm.edu>, multimedia@rah.star-gate.com,
        cvs-committers@freebsd.org
Subject: Re: Ehm. Uh, just what *is* the state of the sound driver in 2.2 and 2.1? 
In-Reply-To: Your message of "Wed, 20 Dec 1995 10:03:07 PST."
             <2026.819482587@time.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Id: <6251.819484608.1@rah.star-gate.com>
Date: Wed, 20 Dec 1995 10:36:48 -0800
From: "Amancio Hasty Jr." <hasty@rah.star-gate.com>
Sender: owner-cvs-committers@freebsd.org
Precedence: bulk

Well, 

Okay, I see your point right now and of course suggestions are always 
welcome and contributions are even more welcome.

You see in order to be able to establish a release plan, people and not
just me or Jim  have to commit themselves to it. It is very difficult
to release something like a sound driver if people are not actively
involved. I can commit to a release plan and just simply drop out
support for all the cards that I don't have. 

To  the folks that are always crying out for support for Creative 
Labs soundcards , I suggest to start sharpening your pencils and to start
getting more involved. If you have questions post. Now, it is a good 
time to start....

	Amancio


>>> "Jordan K. Hubbard" said:
 > > Last but not least I am really surprised at Jordan for even suggesting 
 > > integrating the current alpha sound driver into the CVS tree. 
 > 
 > Hello?!  I never *suggested* any such thing!  I asked if there were
 > any *plans* to do it, you know, any "get it working in 3 weeks, polish it
 > for a week, commit it within the next few weeks after that" sorts of
 > plans.
 > 
 > What we usually do around here is declare that a big snapshot is
 > coming up and everybody then runs around saying "Is the new sound
 > driver better than the old one yet?  Should we jump?" for awhile. If

Gee, we are going to work on a new sound driver which is worse than
the old one.


 > the opinions of yourself and Jim are sufficienty positive, the new
 > sound driver is shoved into the hands of some hapless commit person
 > and inexpertly folded into the tree, from which point forward it
 > either works or it doesn't. :-)
 > 
 > I can certainly see ways in which this process could be improved. :-)
 > 
 > 					Jordan
 > 
 > > I have tried to make it clear that the current alpha sound driver is
 > > intended for sound driver hackers --- that means that is not ready for
 > > general distribution.
 > > 
 > > As for 2.1-current, Julian is more than happy to assist the group to 
 > > integrate the current alpha sound driver with his /devfs stuff.
 > > 
 > > 	Amancio
 > > 
 > > 
 > > 
 >