-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
REMINDER: 3.0 BETA APPROACHING #12899
Comments
Is this fancy logo going to be used for the beta or was that just done For Fun:tm:? |
@NullConstant It's just meant as a reminder image to focus on 3.0 beta :) Actual release will probably have something else. |
Good! |
Glad I looked at this forum. I was JUST going to start porting my game to Godot 3 from 2.X. I guess the wait is almost over :) |
Beta is going to need a full list of features and changes to make bug hunts easier, also to start with new demos. |
alpha2 plugin system is broken. Godot fails to load custom nodes- is that a bug or a missing feature that will make a comeback? |
@blurymind I have no issues with custom nodes. Can you try with a more recent build? If there's a problem, open a new report. |
Could this be fixed? How hard would it be? #11030 |
Regarding this topic #9561, |
Not only this does not really solve the problem, but this also will cause differences in behavior between different monitor Hz (which should never impact how a game's physics and simulation runs). Not to mention that many people forget to use |
We seem to be 91% through the 3.0 milestone. Is this a bug? Should I let Github know? Or should I let reduz bask in the numbers being higher than they should be?
|
Yeah,today is November 20. |
The beta build will be released when it's ready, no ETA. Nov 20 is only the date for the feature freeze. |
Oh, all right |
So, did feature freeze officially happen? |
He just said that feature freeze will be november 20th
…On 20 Nov 2017 18:03, "Nickolai Korshunov" ***@***.***> wrote:
The beta build will be released when it's ready, no ETA. Nov 20 is only
the date for the feature freeze.
So, did feature freeze officially happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12899 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGMbVbpRrnOneScTxXnFja0tXaGzpQPzks5s4b72gaJpZM4Qbq8W>
.
|
What does "feature freeze" mean exactly? |
It means today we are adding a freezing feature for games. Whatever this feature entails is out of my knowledge. |
No new features will be added. So nothing like Mono support, GDNative or VR/AR. Focus will be on fixing bugs. |
@reduz @akien-mga @bruvzg : I think PR #10546 (bidi and text shaping support) can be considered for merge because it is implemented as a separate Control without any modification in other UI nodes. |
This is very important to fix because it causes broken scenes that are tricky to fix #13172 Most users will give up. |
I can still reproduce this. |
Update to latest |
This is a reminder that 3.0 BETA is approaching. Your code must be merged before November 20 (a week from now) or it will have to wait for 3.1, as we will enter Feature Freeze!
The text was updated successfully, but these errors were encountered: