Godot 3.1 in beta, entering release freeze (only major bug fixes accepted) #24822
Comments
|
Shortest beta cycle ever I guess. Thanks and good luck everyone! |
|
I would ask for an explanation in the official release notes , in the godot web page, to especify what compiler, system and flags are used to compile the official builds (included alphas and betas). (I´m unable to get a tiniest and fastest build with msvc2015 in windows no mathers the flags used, no mather link in time optimizations, and all "long time" projects eventually will need to compile the engine with the same performance level that official builds) |
|
@Ranoller Actually @hpvb is working on something even better than documentation; he's going to provide containers (and build script to create containers yourself) that can be used to make builds in the exact same conditions (same compilers, same options) as the official builds. |
|
Call to all core contributors: Please review all 3.1 issues that you are assigned to, and see if they should be worked on ASAP or moved to a later milestone. We need to reduce the count of issues in the 3.1 milestone down to 0 to be ready to release, so I need your help assessing them. If you're not sure whether an issue is critical or can wait for a later milestone, you can ask me. On some issues you assigned yourself, on others you might have been assigned by @reduz or I because we consider that it's an area where you're competent. If we misassigned you, you are of course free to unassign yourself. Here's how to find the issues assigned to you: Or directly in the search bar: Current tally for the 3.1 milestone:
And there are 183 bugs with no assignee yet, and not one of gdscript, rendering or mono. The aim should be to reduce all this drastically over the new few days, as we aim for a release before the end of January (I doubt we'll manage, but it would be really nice so we can at least try to). So please push back anything non critical, and also check if those issues are not fixed already, as many of them are relatively old. I've gone through ~200 issues of backlog myself the last few days, starting from the oldest ones. I'm continuing to make my way up chronologically. |
|
Note: I'm still going through the list myself and kicking stuff to 3.2, so when you click the above links you might have less issues assigned to you than I wrote (or more, if I assigned you more issues in the meantime :)). Feel free to have a look to your issues in the 3.2 milestone to see if there's any must fix that you want to work on now. |
|
So, it's time to wrap up the beta and move to the release candidate stage. I need all core devs to review the current list of opened issues in the 3.1 milestone for "their area", and to decide if they want to keep them in the 3.1 milestone or move to 3.2. Congrats to everyone BTW, the numbers have decreased a lot since my previous post :)
|
|
Closing to reduce the count of pending 3.1 issues :) |
|
By the way, I'm working on mine. Expecting to have it ready along this week. |
Starting now with bcecf56, we're entering the beta stage, and release freeze on the master branch to get ready for releasing Godot 3.1 stable, hopefully by late January 2019.
This means that we will only consider major bug fixes from now on (crash fixes, fixes to very visible bugs that will impact the workflow of most users). Enhancements or non-critical bug fixes will no longer be merged in the master branch until 3.1 is released. Don't worry though, as we will release 3.1.x maintenance releases regularly in following months, where bug fixes and enhancements can be cherry-picked.
Translations strings are also frozen from now on, i.e. no
TTR()string should be added or modified until the release, so that translators can work towards 100% completion for 3.1.Exception to the above rules may happen at the discretion of project or feature maintainers.
Contributors are asked to focus on fixing bugs reported in the 3.1 milestone, as well as enhancing documentation (both class reference here and feature documentation on https://github.com/godotengine/godot-docs). In the coming days, many of the 3.1 issues will be moved to another milestone if they are not considered critical for this release.
We don't have long until the end of January if we want to release 3.1 before GodotCon (and it would be really good to do so, as February/March are usually quite busy due to GDC preparations), so let's all focus on fixing the last blockers.
The text was updated successfully, but these errors were encountered: