Unify pack file version and magic to avoid hardcoded literals.
`version.py` now always includes `patch` even for the first release in
a new stable branch (e.g. 3.2). The public name stays without the patch
number, but `Engine.get_version_info()` already included `patch == 0`,
and we can remove some extra handling of undefined `VERSION_PATCH` this
way.
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
Happy new year to the wonderful Godot community!
We're starting a new decade with a well-established, non-profit, free
and open source game engine, and tons of further improvements in the
pipeline from hundreds of contributors.
Godot will keep getting better, and we're looking forward to all the
games that the community will keep developing and releasing with it.
IMPORTANT: This means that the master branch is now considered feature-complete
for the upcoming 3.2 release, and thus in *feature freeze*.
Unless explicitly allowed by project maintainers, no new feature PRs will be
considered for merge until Godot 3.2-stable is released. Current PRs made
before the feature freeze will still be reviewed and potentially merged before
the beta stage, if deemed satisfactory.
Also include website URL and make it configurable via version.py
together with the rest of the engine branding.
Add mention to MIT license in --help output.
Congratulations to everyone in the Godot community for this awesome new
release, culmination of more than one year of development from close to
500 contributors!
Thanks to all involved, whether you contributed code, documentation,
bug reports, translations, community support or donations. You all
played a role in bringing better free and open source game development
tools to the world!
Godot 3.1 includes more than 7000 commits made since the 3.0 release in
January 2018, 3000 Pull Requests have been merged, and 3000 issues have
been fixed!
This release makes the 3.x branch more stable and powerful, and makes
it a very mature game development tool for both 2D and 3D.
Now feature development can restart towards 3.2 and 4.0!
If it needs to be hardcoded (for the sake of reproducible builds),
it should be together with the other hardcoded version info.
And yeah, two months in, let's move to 2019.
IMPORTANT: This means that the master branch is now considered feature-complete
for the upcoming 3.1 release, and thus in *feature freeze*.
Unless explicitly allowed by project maintainers, no new feature PRs will be
considered for merge until Godot 3.1-stable is released. Current PRs made
before the feature freeze will still be reviewed and potentially merged before
the beta stage, if deemed satisfactory.
Congratulations to everyone in the Godot community for the tremendous work
done on this release since 18 months, with hundreds of contributors pushing
almost 7500 commits with more than 3000 PRs and closing over 2000 issues
(and fixing even more than that, as many work-in-progress bugs were fixed
before an issue could be filled).
Godot 3.0 is definitely our biggest and boldest release so far, and we want
to thank the whole community for their unswerving support during this long
wait.
From there on, there is a lot of work to do to strengthen the foundations
that we built with 3.0, fixing the bugs that the many refactorings probably
introduced, optimizing new features and enhancing the usability again...
The 3.x era should be a fruitful one for Godot, and we hope that you will
continue using it to create awesome 2D and 3D games and increase the
notoriety of your favourite engine in the game development industry.
And now, let's all start waiting for 3.1...
*Feature freeze* means that from now on, no new features will be considered
for Godot 3.0, unless explicitely decided by core developers.
New pull requests implementing additional features will be automatically
set for the 3.1 milestone, and will only be considered for merging once the
3.0 version goes stable and the *master* branch reopens for feature
development.
Existing PRs made before the freeze will still be reviewed and potentially
be merged, if the features that they implement are deemed important enough
or don't risk to introduce issues.
Otherwise, PRs should now focus on:
- Fixing bugs
- Enhancing existing 3.0 features
WARNING: This branch is unstable and should not be used in
production for the time being.
See https://godotengine.org/article/warning-head-going-unstable
for more details.
To get the previous 2.2-alpha unreleased version, you can checkout
the '2.2' branch.
This push changes the binary and XML formats and bumps the major version to 2.0. As such, files saved in this version WILL NO LONGER WORK IN PREVIOUS VERSIONS. This compatibility breakage with older versions was required in order to properly provide project refactoring tools.
If I were you, unless you are brave, I would wait a week or two before pulling, in case of bugs :)
Summary of Changes
-New Filesystem dock, with filesystem & tree view modes.
-New refactoring tools, to change or fix dependencies.
-Quick search dialog, to quickly search any file
-=-==-=-=-=-=-=-
-Small fixes in canvas item light shader
-Fixed compilation in server target
-Export for Android makes 32 bits display as default
-changed version to 1.1beta1
Rémi Verschelde
Joost Heitbrink
Juan Linietsky
Juan Linietsky