Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to start tagging releases #666

Open
hcorion opened this issue Nov 1, 2021 · 6 comments
Open

Request to start tagging releases #666

hcorion opened this issue Nov 1, 2021 · 6 comments

Comments

@hcorion
Copy link

hcorion commented Nov 1, 2021

Cubeb has been used outside of the Mozilla space for a while now, it would be nice if we had a concept of stable releases to allow for consistent use for third parties and for a system cubeb library on unix-based OSes to be shared between the various applications.

@Tachi107
Copy link
Contributor

Tachi107 commented Dec 6, 2021

I'm currently maintaining cubeb in Debian (the package landed yesterday 🎉️), and I have to say that without releases everything is a bit more difficult :/

@kinetiknz
Copy link
Collaborator

Definitely open to doing this, especially with feedback on what'd be most helpful for other (non-Gecko) users.

@Tachi107
Copy link
Contributor

Tachi107 commented Dec 7, 2021

I don't know in terms of features (as I personally don't use cubeb directly), but from a distro perspective predictable ABI and API compatibility (e.g. breaking API, and possibly ABI, compat only with major releases, or breaking ABI only in minor (non-patch) releases, etc) would be really important.

For feature feedbacks you could get in touch with some guys that are creating Nintendo consoles emulators (yuzu, citra, Dolphin), as they all seem to be using cubeb. For example, it seems that they would really like to have multichannel output (yuzu-emu/yuzu#3751), but it seems that you're already tracking this in #178

@kinetiknz
Copy link
Collaborator

We have some breaking API changes planned for early next year, so I'll make a "1.x" branch and tag a stable release from that before making those changes. That branch is likely to see only very minimal maintenance and changes after that point. Firefox will continue to use the latest development version, so generally won't remain compatible with stable releases. Once the breaking API changes settle down, I'll also tag a version of that for release.

@Tachi107
Copy link
Contributor

Sound good, thanks :)

@Tachi107
Copy link
Contributor

Related to #257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants