[evolution-mapi] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 1337bd2... NEWS update for 3.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[evolution-ews] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: d37bdd0... NEWS update for 3.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[evolution] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 5eb0771... NEWS update for 3.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[evolution-data-server] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 7d6f7ee... NEWS update for 3.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: mahjongg, issue with ssh key, can't ship release
On Fri, Mar 6, 2020 at 1:10 am, Alberto Ruiz wrote: I think the best way forward is to take master, bump the meson.build file to 3.36.1 and issue another release to get the latest translations and let the tagged .0 linger? Agreed. Sorry about this folks. PS: (it occurs to me that we should not allow pushing version tags on commits that are not on a branch?) Just made the same mistake earlier today with libgnome-games-support. I mess this up at least once a year. Automated protection sure would be nice ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: mahjongg, issue with ssh key, can't ship release
oops! I think I just messed up, I thought I had pulled, and I didn't and then I just pushed the tag and not the branch, I was too focused on trying to fix the ssh problem and did not do due diligence :/ I think the best way forward is to take master, bump the meson.build file to 3.36.1 and issue another release to get the latest translations and let the tagged .0 linger? Sorry about this folks. PS: (it occurs to me that we should not allow pushing version tags on commits that are not on a branch?) El vie., 6 mar. 2020 a las 0:53, Michael Catanzaro () escribió: > On Fri, Mar 6, 2020 at 12:13 am, Alberto Ruiz wrote: > > In the meantime, I already tagged 3.36.0, if somebody can dist and > > release I'd appreciate it. > > I see it's not on any branch? :( > > > -- Cheers, Alberto Ruiz ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: mahjongg, issue with ssh key, can't ship release
On Fri, Mar 6, 2020 at 12:13 am, Alberto Ruiz wrote: In the meantime, I already tagged 3.36.0, if somebody can dist and release I'd appreciate it. I see it's not on any branch? :( ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: mahjongg, issue with ssh key, can't ship release
On Fri, Mar 6, 2020 at 12:13 am, Alberto Ruiz wrote: In the meantime, I already tagged 3.36.0, if somebody can dist and release I'd appreciate it. I'll do it. Thanks Alberto! ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: mahjongg, issue with ssh key, can't ship release
I am still stuck in the same situation, I sent a ticket to the sysadmins to see if we can find a solution. In the meantime, I already tagged 3.36.0, if somebody can dist and release I'd appreciate it. El dom., 1 mar. 2020 a las 20:59, Alberto Ruiz () escribió: > Thank you both! > > I had a hectic couple of month with the move but now I start to have some > space to do some of my GNOME chores, will do my best to stick around. > > Thanks Abderrahim for your help, appreciate it. > > El dom., 1 mar. 2020 a las 17:38, Michael Catanzaro () > escribió: > >> On Sat, Feb 29, 2020 at 11:30 pm, Alberto Ruiz wrote: >> > I am having issues with my ssh keys, I've updated it in IPA but the >> > change did not propagate. >> >> Alberto! :) Glad you're sticking around. I saw a stranger playing GNOME >> Mahjongg the other day... fun to see GNOME stuff in the wild. >> >> If your new key hasn't propagated by Monday, please ask Andrea to >> investigate. Can't have you locked out! >> >> Thanks Abderrahim for handling the release. >> >> Michael >> >> >> > > -- > Cheers, > Alberto Ruiz > -- Cheers, Alberto Ruiz ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[accerciser] (2 commits) Created branch gnome-3-36
The branch 'gnome-3-36' was created. Summary of new commits: 9175e1e... Add 3.34.x releases to appdata 42f0093... Prepare for 3.36.0 release ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Freeze break request for glib-networking
Hi, I'd like to request a freeze break for: https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/116 which got committed during the freeze period. This just fixes a non-void function that lacked a return value in an old fallback path when compiling with the OpenSSL backend -- which should be disabled at build time almost everywhere -- when using the ancient version of OpenSSL in RHEL 6 era. This surely won't have any impact on anyone using GNOME 3.36, so say yes please. :) Michael ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-sudoku] Created branch gnome-3-34
The branch 'gnome-3-34' was created pointing to: 40afbac... Update British English translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-disk-utility] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 9b59983... Prepare 3.36.0 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-clocks] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 2966f03... Update Punjabi translation ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: [evolution-data-server] Hard code freeze break plea
On Thu, 2020-03-05 at 09:43 -0600, Michael Catanzaro wrote: > On Thu, Mar 5, 2020 at 4:33 pm, Andre Klapper wrote: > > r-t approval 1 of 2. > > Approval 2 Hi, thanks, I just committed it [1]. Bye, Milan [1] https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/127dde9233bb62d59ca486a5610c19fde9ed92c7 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break for USB protection in gnome-session for non-systemd setups
On Thu, Mar 5, 2020 at 2:50 pm, Andre Klapper wrote: Not happy that it's so late, but looks trivial and reasonable. So I'll throw in my release-team approval 1 of 2. Approval 2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: [evolution-data-server] Hard code freeze break plea
On Thu, Mar 5, 2020 at 4:33 pm, Andre Klapper wrote: r-t approval 1 of 2. Approval 2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: [evolution-data-server] Hard code freeze break plea
r-t approval 1 of 2. andre On Thu, 2020-03-05 at 15:15 +0100, Milan Crha via release-team wrote: > Hello, > a user reported an issue [1] in 3.35.92 of evolution-data-server about > missing Google calendars (and tasks), when the account is configured in > GNOME Online Accounts. That's a regression after changes made months > ago. > > I can wait with the fix for 3.36.1, but I'd prefer to have the fix > included in 3.36.0, because Google seems to be particularly popular, > thus having not shown calendars for newly created accounts in GOA would > be considered a problem by early adopters. > > Thus I'd like to ask: can I commit the change for 3.36.0, please? > > The fix is rather trivial [2] and I tested it that it can also fix > already created accounts, thus even users with already created new > accounts will have things fixed silently (after they start patched > evolution-source-registry). > > Thanks and bye, > Milan > > [1] https://gitlab.gnome.org/GNOME/evolution-data-server/issues/198 > [2] > https://gitlab.gnome.org/GNOME/evolution-data-server/issues/198#note_731721 > > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[evolution-data-server] Hard code freeze break plea
Hello, a user reported an issue [1] in 3.35.92 of evolution-data-server about missing Google calendars (and tasks), when the account is configured in GNOME Online Accounts. That's a regression after changes made months ago. I can wait with the fix for 3.36.1, but I'd prefer to have the fix included in 3.36.0, because Google seems to be particularly popular, thus having not shown calendars for newly created accounts in GOA would be considered a problem by early adopters. Thus I'd like to ask: can I commit the change for 3.36.0, please? The fix is rather trivial [2] and I tested it that it can also fix already created accounts, thus even users with already created new accounts will have things fixed silently (after they start patched evolution-source-registry). Thanks and bye, Milan [1] https://gitlab.gnome.org/GNOME/evolution-data-server/issues/198 [2] https://gitlab.gnome.org/GNOME/evolution-data-server/issues/198#note_731721 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: Freeze break for USB protection in gnome-session for non-systemd setups
Not happy that it's so late, but looks trivial and reasonable. So I'll throw in my release-team approval 1 of 2. andre On Thu, 2020-03-05 at 13:08 +0100, Tobias Mueller wrote: > I am asking for an exception to have the following patch included in > GNOME 3.36: > > https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/37 > > It's purpose is to actually start the USB protection daemon in the > non- > systemd case. The patch is simple in that it adds the component to > the > list of things to start up (RequiredComponents). Not including the > patch makes GNOME behave differently under systemd (or non-systemd, > depending on which side of the fence you are standing). > > The maintainers are okay with having it merged and I think the > potential > for regression is lower than the effects of the regression that > currently exists. But of course, that's what everybody thinks when > they > require an exception ;-) > > There are no UI strings involved. > > Cheers, > Tobi > > ___ > release-team@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Freeze break for USB protection in gnome-session for non-systemd setups
Hello Release-Team. I am asking for an exception to have the following patch included in GNOME 3.36: https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/37 It's purpose is to actually start the USB protection daemon in the non- systemd case. The patch is simple in that it adds the component to the list of things to start up (RequiredComponents). Not including the patch makes GNOME behave differently under systemd (or non-systemd, depending on which side of the fence you are standing). The maintainers are okay with having it merged and I think the potential for regression is lower than the effects of the regression that currently exists. But of course, that's what everybody thinks when they require an exception ;-) There are no UI strings involved. Cheers, Tobi ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
