Re: Code freeze break request for GLib
On Thu, Sep 5, 2019 at 5:08 AM, Philip Withnall wrote: I would like to make the GLib 2.62.0 release tomorrow morning (Friday 6th) due to being away from the afternoon onwards. Can I get a couple of approvals before then? Approval 1/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: GNOME Shell freeze break request
On , Iain Lane wrote: I discovered this morning¹ that if you toggle mute/unmute in Shell 3.33.90 then your volume is not restored to what it was before - it's left at 0. The reason is that Shell's volume slider responds to the initial muting by setting itself to empty, but this also triggers the slider's callback to update Pulseaudio with a level of 0. (I also have noticed that when you log in to a new session then the volume is set to 0 each time and this doesn't happen any more with this patch, but I haven't proved that bug so this is more of an aside that the effect might be greater than the mute/unmute case.) We had a similar bug with the brightness slider, which Florian fixed by blocking the signal handlers when updating the slider's value in response to an external change (commit referenced in the below MR). The fix here is the same -it's just that volume case was overlooked earlier. It's already been pre-approved by Carlos (thanks). https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/703 This bug is kind of lame - I think it'd be good to fix for 3.34. This looks like a "paper cut" issue, but the change is small and not very intrusive, so might as well get into 3.34.0. I do hope we have reached the end of the gnome-shell freeze break requests, though. RT 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.
GNOME Shell freeze break request
I discovered this morning¹ that if you toggle mute/unmute in Shell 3.33.90 then your volume is not restored to what it was before - it's left at 0. The reason is that Shell's volume slider responds to the initial muting by setting itself to empty, but this also triggers the slider's callback to update Pulseaudio with a level of 0. (I also have noticed that when you log in to a new session then the volume is set to 0 each time and this doesn't happen any more with this patch, but I haven't proved that bug so this is more of an aside that the effect might be greater than the mute/unmute case.) We had a similar bug with the brightness slider, which Florian fixed by blocking the signal handlers when updating the slider's value in response to an external change (commit referenced in the below MR). The fix here is the same -it's just that volume case was overlooked earlier. It's already been pre-approved by Carlos (thanks). https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/703 This bug is kind of lame - I think it'd be good to fix for 3.34. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] ¹ But someone had already reported https://gitlab.gnome.org/GNOME/gnome-shell/issues/1557 signature.asc Description: PGP signature ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Re: GNOME Shell freeze break request
On Thu, Sep 5, 2019 at 7:45 AM, Emmanuele Bassi wrote: RT approval 1/2. Approval 2/2 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
NetworkManager 1.20.2
News Overview of changes since NetworkManager-1.20.0 === This is a new stable release of NetworkManager. Notable changes include: * Don't ask wpa_supplicant to attempt to enable FT if the interface doesn't support it. * Various bug fixes and improvements. * French, Japanese, Korean, Polish and Simplified Chinese translation updates. Download https://download.gnome.org/sources/NetworkManager/1.20/NetworkManager-1.20.2.tar.xz (4.49M) sha256sum: 514e373f2c46536cacca644af859fb535c7a9ac4988a54d861d76f44c87fac84 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
ДРОБЛЕНИЕ БИЗНЕСА.
18-19 Сентября 2019 г. с 10:00 до 17:30 Промокод: 391 Лицензированный образовательный центр приглашает на обучение: Минимизация налоговых рисков при дроблении бизнеса. Возможно участие посредством online-трансляции. В результате обучения участники: - получат целостное понимание правовых проблем, связанных с дроблением бизнеса, - освоят современные способы разделения организации, - ознакомятся с основными принципами рассмотрения налоговых споров в суде и порядком защиты от претензий налоговых органов, - получат все необходимые для повседневной работы нормативные документы, информационно-справочные материалы, - научатся применять полученную информацию на практике. Вся подробная информация и регистрация участников по телефону в Москве: 8 код (495) телефон 2211169 ( мн-ый ) Адрес: город Москва, бизнес центр, м. Бауманская, ул. Бауманская д.6, стр.2. От метро 5 мин пешком. Всем участникам высылается подробная схема проезда. Вы можете участвовать в обучении как от компании, так и как частное лицо. (пожалуйста не отвечайте на обратный адрес эл.почты) Описание программы: Эволюция правового подхода оценки построения налогоплательщиками группы лиц (дробление бизнеса). - Вывод сотрудников. Аутсорсинг. Способы разделения организации. - Разбор действенных "легенд" в обоснование дробления бизнеса (на основе практики, решений судов). - Переквалификация аутсорсинга, возмездного оказания услуг в трудовые отношения. Разбор ошибок при оформлении документов. - Анализ ошибок допускаемых при аутсорсинге (работа осуществляется без цели извлечения прибыли, является зависимой от головного предприятия и т.п.). - Аутстаффинг. Рассмотрение законопроектов о запрете аутстаффинга. Варианты замены договорной работы. - Основания завышения стоимости работ, услуг, получаемых от вновь созданного предприятия (почему ранее те же работы выполнялись за 10 рублей, а сейчас за 100?). Анализ причин смены "недобросовестного" поставщика на "получение необоснованной выгоды" и "учет операций" с "их действительным экономическим смыслом". - Разбор способа позволяющего защититься от претензий по трансфертному ценообразованию и признании лиц недобросовестными, а саму схему созданной в целях получения необоснованной налоговой выгоды. - Защита от показаний/шантажа сотрудников. - Обход пределов применения УСН с использованием договора простого товарищества. Легенды, обосновывающие заключение такого договора. - Потеря документов, налоговые последствия. - Фактическое нахождение юридического лица не по месту регистрации, либо наличие обособленных подразделений по ст. 55 ГК РФ как основание утраты права на применение УСН. - Сокрытие афиллированности: использование доверенных лиц, оффшоров, некоммерческих организаций. - Передача имущества при дроблении: реорганизация, взнос в уставный капитал, займы и т.п. Судебная практика, выявляющая риски безвозмездной передачи имущества, дарения. - Защита активов - правило "четырех углов". - Способы контроля доверенных лиц как элемент безопасности активов. - Способы управления группой компаний. - Презумпция недобросовестности. - Анализ законодательных инициатив, пресекающих оптимизацию налогов. - Рассмотрение методичек Минфина (ДСП) о выявлении и предъявлении претензий к компаниям осуществившим дробление своей структуры. Новые требования к выездным проверкам и т.д. Последние выявленые схемы по дроблению бизнеса, разбор сложных случаев. Участие составит - 25 800 руб. Участие посредством онлайн-трансляции - 207оо руб. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Freeze break request: Tracker and Tracker-miners
Hello, We have 2 merge requests outstanding for Tracker that we want to merge before 2.3.0. They are related to a new feature, storing MusicBrainz IDs for music files. We found a problem in how it's implemented, and we need to merge these two patches to fix it: https://gitlab.gnome.org/GNOME/tracker/merge_requests/125 https://gitlab.gnome.org/GNOME/tracker-miners/merge_requests/101 Let me know if it's OK to merge them during the code freeze! Thanks ___ 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.
Second Epiphany freeze break request
Hi, Due to some changes in WebKit, some code that could previously be reached only once is now run multiple times. So Epiphany needs to be more careful about not doing one-time things there, like connecting to signals. This commit: https://gitlab.gnome.org/GNOME/epiphany/merge_requests/421/diffs just moves the signal connections to a safer place. Michael ___ 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 for GLib
On Thu, 2019-09-05 at 14:49 +0100, Emmanuele Bassi wrote: > On , mcatanz...@gnome.org wrote: > > On Thu, Sep 5, 2019 at 5:08 AM, Philip Withnall > > wrote: > > > I would like to make the GLib 2.62.0 release tomorrow morning > > > (Friday > > > 6th) due to being away from the afternoon onwards. Can I get a > > > couple > > > of approvals before then? > > > > Approval 1/2 > > 2/2. > > If you can't make a release on Friday, I can do that for you. Merged, thanks! I’m making the GLib 2.62.0 release now (or, failing that, tomorrow morning). Philip signature.asc Description: This is a digitally signed message part ___ 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
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.
3.35/3.36 schedule vs moving Tarballs Due to Fridays
I've created an initial 3.35/3.36 release schedule in https://gitlab.gnome.org/GNOME/releng/commit/9141d8b0c4edba236e8a779b9216805b1caff36b but given that we want to move the Tarballs Due from Mon to Fri in https://mail.gnome.org/archives/desktop-devel-list/2019-August/msg00029.html , the scripts creating the ical and wiki markup still list Monday. Could someone who's better in Python take a look and change the relevant code to go for Fri instead of Mon? Should be somewhere in https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/libschedule.py https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/ical.py https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/wiki.py Thanks in advance, andre -- 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.
Re: Second Epiphany freeze break request
One approval for you On Thu, 5 Sep 2019, 21:22 , wrote: > Hi, > > Due to some changes in WebKit, some code that could previously be > reached only once is now run multiple times. So Epiphany needs to be > more careful about not doing one-time things there, like connecting to > signals. > > This commit: > > https://gitlab.gnome.org/GNOME/epiphany/merge_requests/421/diffs > > just moves the signal connections to a safer place. > > Michael > > > ___ > 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: 3.35/3.36 schedule vs moving Tarballs Due to Fridays
You piqued my curiousity, so I dug around. I think I found the right spot to change it. https://gitlab.gnome.org/GNOME/releng/merge_requests/7 On Thu, Sep 5, 2019 at 7:06 PM, Andre Klapper wrote: I've created an initial 3.35/3.36 release schedule in https://gitlab.gnome.org/GNOME/releng/commit/9141d8b0c4edba236e8a779b9216805b1caff36b but given that we want to move the Tarballs Due from Mon to Fri in https://mail.gnome.org/archives/desktop-devel-list/2019-August/msg00029.html , the scripts creating the ical and wiki markup still list Monday. Could someone who's better in Python take a look and change the relevant code to go for Fri instead of Mon? Should be somewhere in https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/libschedule.py https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/ical.py https://gitlab.gnome.org/GNOME/releng/blob/master/tools/schedule/wiki.py Thanks in advance, andre -- 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. ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
libsigc++ 3.0.0
News This is the first stable release of sigc++-3.0, installable in parallel with sigc++-2.0. Changes compared to the latest unstable release: * Fix tuple_transform_each() for libc++ (Kjell Ahlstedt) Issue #25 (Jeff Trull) Documentation: * Remove some obsolete documentation (Kjell Ahlstedt) Tests: * Make test_track_obj.cc compile with clang++ (Kjell Ahlstedt) * Don't call static method via instance (Murray Cumming) ChangeLog = https://download.gnome.org/sources/libsigc++/3.0/libsigc++-3.0.0.changes (1.34K) Download https://download.gnome.org/sources/libsigc++/3.0/libsigc++-3.0.0.tar.xz (976K) sha256sum: 50a0855c1eb26e6044ffe888dbe061938ab4241f96d8f3754ea7ead38ab8ed06 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
Code freeze break request for GLib
Hi all, Christian has a nice fix for a bug with some of the new GDateTime API for file attributes, which eases porting from g_file_info_get_modification_time() to g_file_info_get_modification_date_time(). https://gitlab.gnome.org/GNOME/glib/merge_requests/1087 I’d like to get this into 2.62, since it means the new API doesn’t require people to add G_FILE_ATTRIBUTE_TIME_MODIFIED_USEC to their GFileInfo queries to keep things working. It’s a low-risk fix, and I’ve requested that a unit test be added. I would like to make the GLib 2.62.0 release tomorrow morning (Friday 6th) due to being away from the afternoon onwards. Can I get a couple of approvals before then? Thanks, Philip signature.asc Description: This is a digitally signed message part ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
[gnome-build-meta] Created branch gnome-3-34
The branch 'gnome-3-34' was created pointing to: d4b898a... GNOME 3.33.92 ___ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
