Skip to content

Merge 'next' branch into master #1329

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

Closed
TobiasScharnowski opened this issue Sep 17, 2020 · 7 comments
Closed

Merge 'next' branch into master #1329

TobiasScharnowski opened this issue Sep 17, 2020 · 7 comments

Comments

@TobiasScharnowski
Copy link

There seems to be a bit of a deviation between the two branches 'next' and 'master'. Among others, the binding support differs between the two branches.

Is there a distinct reason for keeping the branches separate? Otherwise, merging the two would be nice to unify the functionality.

@aquynh
Copy link
Member

aquynh commented Sep 17, 2020 via email

@google-mirror
Copy link

We plan to merge after 1.0.2 release

Did those bugs reported by Google AutoFuzz get fixed?

@domenukk
Copy link
Contributor

Any updates on this? Thanks :)

@aquynh
Copy link
Member

aquynh commented Nov 17, 2020 via email

@domenukk
Copy link
Contributor

So what's the deal here: will next ever end up in main?

@wtdcode
Copy link
Member

wtdcode commented Jun 25, 2021 via email

@wtdcode
Copy link
Member

wtdcode commented Oct 3, 2021

Closed due to uc2 beta release.

@wtdcode wtdcode closed this as completed Oct 3, 2021
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

5 participants