From: Jaroslav Kysela <perex@perex.cz>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: Packages 1.0.30 - release pending
Date: Sun, 11 Oct 2015 21:08:01 +0200 [thread overview]
Message-ID: <561AB391.6030504@perex.cz> (raw)
Hi all,
I would like to release 1.0.30 version of all packages. Things to discuss:
1) tinycompress
- do the release this library, too ?
- versioning - follow the rule for all other ALSA packages
(all packages have same version) ?
2) user-space versioning - change the numbering scheme ?
Basically, there aren't major rewrites of API last years and it won't
probably happen quickly. Some APIs might be redesigned - simplified
(mostly the mixer stuff), but I would propose to go from 1.0.x to 1.x
numbering (starting with 1.1) and when a major rewrite of API will be
included, we may change the first (major) version number. The release
frequency is not high, so it won't hurt anything in my eyes. Comments,
objections ? This discussion may end with 1.1 release instead 1.0.30.
Thanks,
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next reply other threads:[~2015-10-11 19:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 19:08 Jaroslav Kysela [this message]
2015-10-12 8:24 ` Packages 1.0.30 - release pending Takashi Iwai
2015-10-12 8:56 ` Koul, Vinod
2015-10-12 9:51 ` Jaroslav Kysela
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=561AB391.6030504@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox