Skip to contentSkip to conversation

v1.1.2 release?

DISCUSSION Takashi Iwai 3 participants 5 messages Jul 25, 2016 – Jul 26, 2016

lore
Share & tools
lore
#0 lore raw

Hi Jaroslav,

shall we release v1.1.2 along with 4.7 kernel? We've got already a bunch of changes in alsa-lib and co.

thanks,

Takashi

#1 lore raw

Dne 25.7.2016 v 11:58 Takashi Iwai napsal(a):

Quoted 4 lines

Hi Jaroslav,

shall we release v1.1.2 along with 4.7 kernel? We've got already a bunch of changes in alsa-lib and co.

Hi,

yes, I plan to prepare the new release this week.

Thanks,
Jaroslav

Signature · 2 lines
Jaroslav Kysela <[email protected]>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
#2 lore raw

Hi Jaroslav and Iwai-san,

Quoted 9 lines · Jaroslav Kysela

Dne 25.7.2016 v 11:58 Takashi Iwai napsal(a):

Quoted 4 lines

Hi Jaroslav,

shall we release v1.1.2 along with 4.7 kernel? We've got already a bunch of changes in alsa-lib and co.

Hi,

yes, I plan to prepare the new release this week.

In this release, I added five APIs newly:
* snd_ctl_elem_info_set_dimension()
* snd_ctl_add_integer_elem_set()
* snd_ctl_add_integer64_elem_set()
* snd_ctl_add_boolean_elem_set()
* snd_ctl_add_enumerated_elem_set()
* snd_ctl_add_bytes_elem_set()

In this case, on usual way to maintain library, as long as I know, minor version is going to be incremented, instead of micro version. In short, to v1.2.0.

But I committed assuming v1.1.2. For example:
http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/control/control.c;h=6c00b8e50d2be78f9c5e93322b8e8b107ff8c442;hb=HEAD#l2533

If it's going to be versioned to v1.2.0, please tell it to me. I'll post a patch to fix my commits in time of your release work.

Thanks

Takashi Sakamoto

#3 lore raw
Quoted 22 lines · Takashi Sakamoto

Hi Jaroslav and Iwai-san,

Quoted 9 lines · Jaroslav Kysela

Dne 25.7.2016 v 11:58 Takashi Iwai napsal(a):

Quoted 4 lines

Hi Jaroslav,

shall we release v1.1.2 along with 4.7 kernel? We've got already a bunch of changes in alsa-lib and co.

Hi,

yes, I plan to prepare the new release this week.

In this release, I added five APIs newly:
* snd_ctl_elem_info_set_dimension()
* snd_ctl_add_integer_elem_set()
* snd_ctl_add_integer64_elem_set()
* snd_ctl_add_boolean_elem_set()
* snd_ctl_add_enumerated_elem_set()
* snd_ctl_add_bytes_elem_set()

Quoted 3 lines

In this case, on usual way to maintain library, as long as I know, minor version is going to be incremented, instead of micro version. In short, to v1.2.0.

Good point. Although the minor/tiny version number rule is somewhat ambiguous that people don't care much (as long as it's incremental), it's still helpful to leave a number place for the further corrections. We had to release a version like v1.0.21a in the past. By releasing with the minor version bump, we may still release v1.2.1 soon after once if there is some build error or such a correction is needed.

Quoted 5 lines

But I committed assuming v1.1.2. For example:
http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/control/control.c;h=6c00b8e50d2be78f9c5e93322b8e8b107ff8c442;hb=HEAD#l2533

If it's going to be versioned to v1.2.0, please tell it to me. I'll post a patch to fix my commits in time of your release work.

They can be corrected easily here, too, hence no need to submit the patch. It'd be a one-liner scripting, after all.

thanks,

Takashi

#4 lore raw
Quoted 28 lines · Takashi Iwai
Quoted 22 lines · Takashi Sakamoto

Hi Jaroslav and Iwai-san,

Quoted 9 lines · Jaroslav Kysela

Dne 25.7.2016 v 11:58 Takashi Iwai napsal(a):

Quoted 4 lines

Hi Jaroslav,

shall we release v1.1.2 along with 4.7 kernel? We've got already a bunch of changes in alsa-lib and co.

Hi,

yes, I plan to prepare the new release this week.

In this release, I added five APIs newly:
* snd_ctl_elem_info_set_dimension()
* snd_ctl_add_integer_elem_set()
* snd_ctl_add_integer64_elem_set()
* snd_ctl_add_boolean_elem_set()
* snd_ctl_add_enumerated_elem_set()
* snd_ctl_add_bytes_elem_set()

Quoted 3 lines

In this case, on usual way to maintain library, as long as I know, minor version is going to be incremented, instead of micro version. In short, to v1.2.0.

Quoted 7 lines

Good point. Although the minor/tiny version number rule is somewhat ambiguous that people don't care much (as long as it's incremental), it's still helpful to leave a number place for the further corrections. We had to release a version like v1.0.21a in the past. By releasing with the minor version bump, we may still release v1.2.1 soon after once if there is some build error or such a correction is needed.

Yes. Of cource, we can have our own release policy, however following to the usual way makes it easy for users or developers to get purpose of the release.

Quoted 8 lines
Quoted 5 lines

But I committed assuming v1.1.2. For example:
http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/control/control.c;h=6c00b8e50d2be78f9c5e93322b8e8b107ff8c442;hb=HEAD#l2533

If it's going to be versioned to v1.2.0, please tell it to me. I'll post a patch to fix my commits in time of your release work.

They can be corrected easily here, too, hence no need to submit the patch. It'd be a one-liner scripting, after all.

OK. Thanks.

Takashi Sakamoto