ba46a1cf54
Currently we periodically check for updated extensions, prepare an update and perform it at the next login. This is largely due to the fact that once an extension has been loaded, its code is cached and reloading it would only make it *appear* as updated, while in reality still running the old code. Of course this only applies *once* we have loaded extensions. Before that, it's possible to download and install updates, and only then initialize extensions with their latest version. The trade-off is that network requests, data download and extraction may introduce a significant delay before extensions are enabled. Most extensions modify the UI one way or another, so that delay would likely be noticeable by the user. Assuming that users are usually happy enough with the current extension version, that trade-off doesn't seem worthwhile. However there is an exception: After a major version update, extensions are likely disabled as out-of-date, or at least more likely to break (when the version check is disabled). In that case delaying extension initialization to download and install updates looks like the better trade-off, so do that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2951>
GNOME Shell
GNOME Shell provides core user interface functions for the GNOME desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience.
For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see the project wiki.
Bugs should be reported to the GNOME bug tracking system. Please refer to the Schedule wiki page to see the supported versions.
Contributing
To contribute, open merge requests at https://gitlab.gnome.org/GNOME/gnome-shell.
Commit messages should follow the GNOME commit message
guidelines. If a merge request
fixes an existing issue, it is good practice to append the full issue URL
to each commit message. Try to always prefix commit subjects with a relevant
topic, such as panel: or status/network:, and it's always better to write
too much in the commit message body than too little.
Default branch
The default development branch is main. If you still have a local
checkout under the old name, use:
git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
License
GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.