From: Jaroslav Kysela <perex@perex.cz>
To: "Koul, Vinod" <vinod.koul@intel.com>, "tiwai@suse.de" <tiwai@suse.de>
Cc: "liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Packages 1.0.30 - release pending
Date: Mon, 12 Oct 2015 11:51:21 +0200 [thread overview]
Message-ID: <561B8299.2090200@perex.cz> (raw)
In-Reply-To: <1444640191.3544.11.camel@intel.com>
Dne 12.10.2015 v 10:56 Koul, Vinod napsal(a):
> On Mon, 2015-10-12 at 10:24 +0200, Takashi Iwai wrote:
>> On Sun, 11 Oct 2015 21:08:01 +0200,
>> Jaroslav Kysela wrote:
>>>
>>> Hi all,
>>>
>>> I would like to release 1.0.30 version of all packages. Things to discuss:
>>
>> There are pending issues: one is about the topology ABI and this seems
>> still in flux. I suppose this will be stabilized in 4.4. Also, the
>> documentation for BAT is utterly missing, and I expect we'll get this
>> soonish. Liam, Mengdong, any comments on these?
>>
>> We've discussed a bit about the user-space package release in the
>> meeting. Most people prefer more regular release. My own preference
>> is to stick with the kernel release cycle -- as most of features are
>> related with the update of kernel ABI. It's not necessarily at every
>> kernel but, e.g. with two kernel releases, so that we'll get two or
>> three releases per year. It's just my $0.02, not insisting on it,
>> though.
>>
>>
>>> 1) tinycompress
>>> - do the release this library, too ?
>>
>> Yeah, this was requested in the meething, too.
>
> Thanks that will be great..
>
>>
>>> - versioning - follow the rule for all other ALSA packages
>>> (all packages have same version) ?
>>
>> Vinod?
>
> Sure, so you guys want me to bump up the version to 1.0.30. I don't think that should
> be an issue to align?
Ok, fine. I just asked.
> Also Takashi was mentioning tar balls, do you need me to generate these and upload ?
I'll generate them using my tools on the server. I also prepare the
runtime snapshots - http://www.alsa-project.org/snapshot/ , so you may
test the tarbar before it's versioned. I'll post a note when finished.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2015-10-12 9:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 19:08 Packages 1.0.30 - release pending Jaroslav Kysela
2015-10-12 8:24 ` Takashi Iwai
2015-10-12 8:56 ` Koul, Vinod
2015-10-12 9:51 ` Jaroslav Kysela [this message]
2015-10-12 9:23 ` Liam Girdwood
2015-10-27 15:16 ` Takashi Iwai
2015-10-27 15:27 ` Liam Girdwood
2015-10-27 16:01 ` Jaroslav Kysela
2015-10-27 16:40 ` Liam Girdwood
2015-10-29 1:23 ` Vinod Koul
2015-10-28 15:06 ` Lin, Mengdong
2015-11-04 14:29 ` Jaroslav Kysela
2015-11-04 16:17 ` Liam Girdwood
2015-11-05 3:08 ` Lin, Mengdong
2015-11-05 13:04 ` Mengdong Lin
2015-11-05 13:12 ` Jaroslav Kysela
2015-11-05 13:18 ` Takashi Iwai
2015-11-05 13:33 ` Jaroslav Kysela
2015-11-05 13:38 ` Takashi Iwai
2015-11-05 14:43 ` Lin, Mengdong
2015-11-05 13:07 ` Mengdong Lin
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=561B8299.2090200@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/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.