All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Daniel Mack <zonque@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA release cycle
Date: Fri, 07 Sep 2012 14:51:10 +0200	[thread overview]
Message-ID: <5049EDBE.2090005@canonical.com> (raw)
In-Reply-To: <5049E164.3000405@gmail.com>

On 09/07/2012 01:58 PM, Daniel Mack wrote:
> On 07.09.2012 13:38, David Henningsson wrote:
>> Hi,
>>
>> At Plumber's we discussed the ALSA release cycle. Our releases recently
>> have been irregular, and the reasoning behind why a release was done at
>> that time, has not been very obvious.
>>
>> IIRC, we kind of leaned towards releasing every six months. I don't
>> remember if there was any consensus about whether to try to align this
>> cycle to something else (e g Gnome, KDE, Fedora, Ubuntu, etc), or not.
>
> ... or the kernel? At least for the kernel parts of ALSA, syncing an
> ALSA version to kernel version would automatically tell us which patches
> will make it into a new release. Plus, it would also be easier to
> compare feature sets (something like "ALSA 1.0.26 gives us what we have
> in kernel 3.6").
>
> Would that be feasible or am I missing something?

I took that up as an alternative. I think more people leaned towards six 
month cycles, but it's still an open question.

To me, I also think aligning releases to the kernel makes sense, but 
it'll also mean a lot of releases with little change in, so maybe six 
month cycles are better for that reason.


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  reply	other threads:[~2012-09-07 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 11:38 ALSA release cycle David Henningsson
2012-09-07 11:58 ` Daniel Mack
2012-09-07 12:51   ` David Henningsson [this message]
2012-09-07 13:21     ` Takashi Iwai
2012-09-08 10:52     ` Daniel Mack
2012-09-07 12:53 ` Jaroslav Kysela

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=5049EDBE.2090005@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=zonque@gmail.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.