Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	"Lin, Mengdong" <mengdong.lin@intel.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	Vinod Koul <vinod.koul@intel.com>
Subject: Re: Packages 1.0.30 - release pending
Date: Mon, 12 Oct 2015 10:24:19 +0200	[thread overview]
Message-ID: <s5hvbaca40c.wl-tiwai@suse.de> (raw)
In-Reply-To: <561AB391.6030504@perex.cz>

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.

>    - versioning - follow the rule for all other ALSA packages
>      (all packages have same version) ?

Vinod?

> 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.

Honestly speaking, not many people do care about the version number
nowadays as long as it increases :)  But yes, I find your proposal
good.  A minor update between regular release may still get a version
number like 1.3.1, instead of the current 1.0.28a.


thanks,

Takashi

  reply	other threads:[~2015-10-12  8:24 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 [this message]
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=s5hvbaca40c.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=perex@perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox