Dne 9.3.2016 v 08:52 Takashi Iwai napsal(a): > 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. I agree. I'll release ALSA packages in the week after 4.5 kernel release (next week?). And I (we) can do a decision after every kernel release, if we have enough changes (or there are any required changes to support new kernels). Thanks, Jaroslav -- Jaroslav Kysela <perex@xxxxxxxx> Linux Sound Maintainer; ALSA Project; Red Hat, Inc. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
