On Mar 9 2016 16:52, Takashi Iwai wrote:
On Wed, 09 Mar 2016 08:47:09 +0100,
Takashi Sakamoto wrote:
Hi,
On Mar 9 2016 15:17, Takashi Iwai wrote:
On Wed, 09 Mar 2016 07:16:24 +0100,
Vinod Koul wrote:
On Tue, Mar 08, 2016 at 05:49:19PM +0100, Takashi Iwai wrote:
Hi,
in the previous meeting, there have been requests about the regular
"predictable" release of alsa-lib. We thought of aligning with kernel
release cycle, judging from the nature of alsa-lib.
As a quick glance of the number of commits per month (see in the end of
this message), alsa-lib is not so actively developed recently. (except
for topology APIs)
I think releasing every 2 months makes the release maintenance effort
more hard than its actual advantage. It better to release alsa-lib for 2
or more kernel release cycles.
Yes, that was the proposal in the meeting. It wasn't meant to release
every cycle.
The point is to align with the kernel release cycle so that people can
know the possible release point beforehand. The actual release can be
skipped easily if nothing happens, of course.
To me, it doesn't mean _scheduled_ release. It's just within a policy
for releasing about an aspect of 'date'.
Anyway, I have no objections about it, as long as the cycle is not so
frequent and people are not so busy for the release maintenance.
Regards
Takashi Skamaoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
