From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
Joern Nettingsmeier <nettings@folkwang-hochschule.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: future ALSA development
Date: Mon, 30 Jun 2003 12:17:53 +0200 [thread overview]
Message-ID: <s5hy8zjlvhq.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306241956240.1838-100000@pnote.perex-int.cz>
At Tue, 24 Jun 2003 20:28:08 +0200 (CEST),
Jaroslav wrote:
>
> > i believe, if we change the configuration syntax, it would be better
> > to branch the development tree (or jump the version number).
> > the current system works well already in many fields, so it's nice to
> > keep the stable series.
>
> We can do it when we need to break the compatibility behaviour.
hmm, i think we need now some release engineering.
ALSA 0.9.x series has been released as the STABLE line, and that means
that the API should be kept as much as possible. i don't think it's good
to include the experimental code for a fundamental change to such a
tree (even in cvs).
i know it's a bit annoying to keep both different cvs branches
up-to-date. but now it's the time to separate clearly what we've done
and what we'll do. this will make it easy to release the newer 0.9.x
tarball, too.
well, if we were to use bitkeeper, it would be easier to keep the different
trees in sync... :)
Takashi
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
next prev parent reply other threads:[~2003-06-30 10:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 19:10 future ALSA development Jaroslav Kysela
2003-06-23 11:14 ` Takashi Iwai
2003-06-23 12:01 ` Jaroslav Kysela
2003-06-23 13:13 ` Takashi Iwai
2003-06-23 13:41 ` Paul Davis
2003-06-23 13:51 ` Takashi Iwai
2003-06-23 14:18 ` Paul Davis
2003-06-23 22:22 ` Joern Nettingsmeier
2003-06-24 7:51 ` mru
2003-06-24 8:14 ` Jaroslav Kysela
2003-06-24 11:19 ` Abramo Bagnara
2003-06-24 11:43 ` Paul Davis
2003-06-24 11:56 ` Jaroslav Kysela
2003-06-24 12:16 ` Paul Davis
2003-06-24 17:11 ` Takashi Iwai
2003-06-24 18:28 ` Jaroslav Kysela
2003-06-25 17:49 ` PCMCIA In Kernel Or In ALSA Driver? Len Moskowitz
2003-06-25 18:51 ` Jaroslav Kysela
2003-06-30 10:17 ` Takashi Iwai [this message]
2003-06-24 8:28 ` future ALSA development iriXx
2003-07-03 13:39 ` Kai Vehmanen
2003-07-07 11:26 ` Takashi Iwai
2003-10-01 9:37 ` ALSA in embedded use (was: Re: future ALSA development) Kai Vehmanen
2003-10-01 13:13 ` Takashi Iwai
2003-06-24 12:52 ` future ALSA development Giuliano Pochini
2003-06-24 13:04 ` Jaroslav Kysela
2003-06-24 17:12 ` Takashi Iwai
2003-07-03 14:21 ` Kai Vehmanen
2003-07-03 14:36 ` Kai Vehmanen
2003-07-03 16:05 ` Thomas Charbonnel
2003-07-07 11:37 ` Takashi Iwai
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=s5hy8zjlvhq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=nettings@folkwang-hochschule.de \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
/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.