-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
We plan to merge after 1.0.2 release
|
Did those bugs reported by Google AutoFuzz get fixed? |
Any updates on this? Thanks :) |
I synced next with master just now.
|
So what's the deal here: will |
The next branch is depreciated as of current development. Stay tuned for Unicorn2!
Link to #1217
…________________________________
From: Dominik Maier ***@***.***>
Sent: Friday, June 25, 2021 8:35:38 PM
To: unicorn-engine/unicorn ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [unicorn-engine/unicorn] Merge 'next' branch into master (#1329)
So what's the deal here: will next ever end up in main?
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1329 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHJULO5CYHILBZE4L7KWXILTURZZVANCNFSM4RQOFREQ>.
|
Closed due to uc2 beta release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: