Re: UI Freeze Break Request for GNOME Initial Setup
I am +1 for this too On Fri, Aug 24, 2018 at 2:56 PM wrote: > > I'll give a hesitant +1 here. (You also need a second approval.) > > * Please consider Will's concern about the network appearing to > disappear after it's selected. That doesn't seem like a great user > experience. > > * Use of NetworkManager in gnome-initial-setup is a known cause of > crashers in the past, and there's not really any way to recover the > first boot experience after that happens. So be careful. > > But the benefits do seem worth the late freeze break. > > Michael > > ___ > gnome-doc-list mailing list > gnome-doc-l...@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Code freeze break request: backwards compatibility fix
+1 from me as well On Tue, Aug 28, 2018 at 10:12 AM wrote: > > Looks like this is important. Approval 1 of 2 > > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: gnome-software string freeze break request
I asked for this, so +1 from me. On Fri, Sep 14, 2018 at 8:07 AM Kalev Lember via gnome-doc-list < gnome-doc-l...@gnome.org> wrote: > Hi, > > I would like to backport a commit from git master to gnome-3-30 that > fixes a number of notification issues in gnome-software: > > > https://gitlab.gnome.org/GNOME/gnome-software/commit/f915a08f5a2d7952bdc44a66e4a21503ef9c5b53 > > It breaks the string freeze and adds the following strings (mostly > adding singular forms of existing strings): > > "%s has been updated." > "Please restart the application." > "%s and %s have been updated." > "%u application requires a restart." > "Includes %s, %s and %s." > > Thanks, > Kalev > ___ > gnome-doc-list mailing list > gnome-doc-l...@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: GNOME Boxes | Feature Freeze
Seconded, +1 from me as well On Thu, Feb 21, 2019 at 11:29 AM wrote: > > It's getting kinda late in the cycle for changes like this, but it > doesn't look like too much code. I'll give +1 of 2 release team. > > Michael > > ___ > gnome-doc-list mailing list > gnome-doc-l...@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Update your libhandy submodules (and packages)
On Fri, Mar 1, 2019 at 8:42 AM Bastien Nocera wrote: > > > We don't really have any formal rules for external dependencies, I > > think not since the GNOME 2 days. > > I'll bear that in mind next time I get a complaint about the required > version of meson being too new *cough* ;) > > > I did raise concerns about widespread dependencies on an unstable, in-progress library. And I cautioned against adding libhandy to runtimes. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
notes from thessaloniki meeting
Here are the notes I took before my laptop ran out of power. Sorry that this is very cursory --- achievements in the last year: - gnome runtime with release - request to be notified about build and dependency changes in core modules (Emmanuele) topics: - schedule changes - stable runtime update - release schedule in general - add a translator deadline ? - switch from tarballs to git tags - do we need evtags instead of plain tags ? - signed tags - requiring ci need changes to gitlab ci needed ci runner need to run ftpadmin install - ci for gnome-build-meta need to be easier for people to change gnome-build-meta - gnome-continuous replacement gnome os bof on monday - gnome-software is an issue ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Code freeze break request
Looks fine to me too. approval 2/2 On Tue, Sep 3, 2019 at 11:18 AM Emmanuele Bassi wrote: > On , mcatanz...@gnome.org wrote: > > Hi, > > > > I'd like to request code freeze break to merge this fix: > > > > https://gitlab.gnome.org/GNOME/epiphany/merge_requests/419/diffs > > > > It might fix (a) a bug causing various Epiphany features to break, and > > (b) some UI process memory corruption. Should be very low-risk since > > it's only two lines. > > The change looks good to me, and seems innocuous on its own, so 1/2 RT > approvals from me. > > Ciao, > Emmanuele. > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: String & UI Freeze break request for GNOME Shell
On Tue, Sep 3, 2019 at 2:05 PM Georges Basile Stavracas Neto via release-team wrote: > To the Release Team, > > I hereby ask for String and UI freeze break exceptions for landing GNOME > Shell's > https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/675. This merge > request is an important last step for feature-completeness of the ability > to create > and delete folders within GNOME Shell. > > Tentatively ok with it, but I left a comment. And since this has some string additions, please also ask gnome-i...@gnome.org for their ok. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request to fix gnome-initial-setup
Approval 2/2 On Wed, Sep 4, 2019 at 11:14 AM wrote: > > Approval +1 / 2 for both changes > > > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze exceptions for mutter and gnome-shell
On Wed, Sep 4, 2019 at 1:30 PM Jonas Ådahl via release-team < release-team@gnome.org> wrote: > Here are some freeze exception requests for mutter and gnome-shell: > > Thanks for the detailed explanations. That helps in judging the requests. The middle two MRs are unpleasantly large, but I'll give you approval 1/2, since they all look carefully done and reviewed by the shell team. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break request: Tracker and Tracker-miners
Approval 2/2 On Thu, Sep 5, 2019 at 1:03 PM wrote: > > Looks fine, approval 1/2 > > > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze exception request: gnome-shell
approval 2/2 On Mon, Sep 9, 2019 at 12:22 PM Emmanuele Bassi wrote: > On , Carlos Garnacho wrote: > > Hi!, > > > > Here's another gnome-shell bug that might nice to have soon: > > https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/706 > > > > Impact is low, and tested correct, even if the related issue was not > > verified fixed. > > Indeed, let's avoid borking the shell by reading past NUL bytes. > > Approval 1/2. > > Ciao, > Emmanuele. > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. > ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break exception for the new lock screen
On Tue, Jan 28, 2020 at 1:37 PM Allan Day wrote: > Michael Catanzaro wrote: > > > Would it be possible to arrange a freeze exception for the lock > > > screen work, so we can plan on having another week to get it merged? > > > We don't expect there to be any new strings and I'm happy to > > > coordinate with docs and marketing. > > > > Certainly possible, but it is wise? > > That is the question, and I'm not 100% sure. > > It is equally not smart to never land the things we've worked on for years just because we put ourselves under the pressure of yet another deadlne. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break exception for the new lock screen
On Fri, Feb 14, 2020 at 1:17 PM Michael Catanzaro wrote: > On Fri, Feb 14, 2020 at 10:10 am, Allan Day wrote: > > I thought we got the freeze break. We did get it, didn't we?! > > No, you need two approvals to break the freeze, but you only received a > single approval from me. Somebody else would need to give a second > approval. > > I'm in favor of landing this. So here's your second approval ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
GNOME 3.34.4
Hi, here is another stable GNOME update: GNOME 3.34.4. This release contains several weeks worth of bug fixes, and should be a very safe upgrade from 3.34.3. The GNOME flatpak runtime has been updated as well There next (and last) stable 3.34 update is planned for end of March, seehttps://wiki.gnome.org/ThreePointThirtyfive If you want to compile GNOME 3.34.4, you can use the official BuildStream project snapshot: https://download.gnome.org/teams/releng/3.34.4/gnome-3.34.4.tar.xz The list of updated modules and changes is available here: https://download.gnome.org/core/3.34/3.34.4/NEWS The source packages are available here: https://download.gnome.org/core/3.34/3.34.4/sources/ Enjoy the new release, Matthias Clasen, GNOME Release Team ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
