On Fri, Sep 16 2022 at 04:16:33 PM +0200, Jan Alexander Steffens via
desktop-devel-list wrote:
Arch changes prerelease versions as well, but we have to remove the
period (40.rc -> 40rc) so that it orders before 40 or 40.0.
A tilde is handled the same as a period and would not help us.
Oh,
On Fri, Sep 16 2022 at 10:03:49 AM -0400, Jeremy Bicha
wrote:
I think we could save everyone some work by just making the tilde
style official instead of periods for pre-releases.
That sounds good to me. I like the tilde better anyway.
___
On Fri, Sep 16 2022 at 07:41:10 AM +0200, Milan Crha via
desktop-devel-list wrote:
3.47.0.90 ... GNOME's .alpha
3.47.0.91 ... GNOME's .beta
3.47.0.92 ... GNOME's .rc
... here's a gap for urgent development releases up to
.99
3.47.1... GNOME's .0, aka the
Hi,
GNOME 42.3 is now available. This is a stable bugfix release for GNOME
42. All operating systems shipping GNOME 42 are encouraged to upgrade.
If you want to compile GNOME 42.3, you can use the official BuildStream
project snapshot:
Hi developers,
TL;DR: tarball deadline for 43.alpha is extended by one week to
Saturday, July 9. Tarball deadline for 42.3 and 41.8 remains tomorrow,
July 2.
GNOME 43 is currently in bad shape for a couple reasons:
* The freedesktop-sdk 22.08 update that landed yesterday broke glibc
due to
On Wed, Jun 29 2022 at 11:00:13 PM +, Release Team
wrote:
Tarballs are due on 2022-07-02 before 23:59 UTC for the GNOME 43.alpha
newstable release, which will be delivered next week. In order to
ensure adequate testing, core modules should try to release according
to the unstable schedule
On Wed, Jun 22 2022 at 09:36:06 PM +0200, Marcus Lundblad via
desktop-devel-list wrote:
One option I think is to drop the contact address lookup in Maps (we
use e-d-s via libfolks to match searches on contacts who have
addresses).
That's what I would do for the time being; otherwise, Maps is
and uneventful upgrade from earlier versions of GNOME
42.
Enjoy,
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
and uneventful upgrade from earlier versions of GNOME
41.
Enjoy,
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Reading through the linked issues, nobody has bisected gettext yet to
identify what changed. That's probably the next step towards getting
this fixed.
Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
Hi, feel free to request a freeze break here:
https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues
Seems worth it to me.
Michael
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
of life, and will receive no further updates. It's time to
upgrade to GNOME 41 or GNOME 42 (to be released tomorrow).
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman
On Sun, Mar 13 2022 at 11:00:10 PM +, Release Team
wrote:
Soft translation deadline is 2022-03-16 at 23:59 UTC. Translations
committed after this point may be too late to be included. Maintainers
should not release stable tarballs until after this day.
Hi all,
Just wanted to remind you
Hi Andrea, I've pushed all the screenshots here:
https://gitlab.gnome.org/Infrastructure/static-web/-/commit/d205056a93ab19e53afbb1fe53310d71d7f0afd1
so it should be easy to set up a redirect now. I've also submitted MRs
to all affected apps to transition them from using the people.gnome.org
On Wed, Mar 9 2022 at 06:07:18 PM +0100, Andrea Veri
wrote:
Adding redirects once the service is down is a viable option, you can
push those images to static.g.o and we can add a redirect afterwards
to make sure stuff won't break. Let me know whether that works for
you, thanks!
Oh OK, yes
On Wed, Mar 9 2022 at 05:44:04 PM +0100, Andrea Veri
wrote:
With that in mind and unless anyone within the community objects with
a good rationale we'll be retiring the service by the 31th of March.
Sadly I have images for appstream metadata hosted here (seemed like a
good idea back in 2014,
://download.gnome.org/core/40/40.8/sources/
GNOME 40.8 is designed to be a boring bugfix update for GNOME 40, so it
should be safe to upgrade from earlier versions of GNOME 40.
Enjoy,
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
On Fri, Nov 5 2021 at 09:10:18 AM +0100, Milan Crha via
desktop-devel-list wrote:
Hi,
the NEWS file says the gnome-autoar had been downgraded, while there
had been a new release almost a week ago. Is that a bug or it was
intentional downgrade?
Bye,
Milan
I think we
to upgrade from earlier versions of GNOME 40.
Enjoy,
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Hi maintainers,
It looks like our usual release reminder mail did not go out this week
for some reason. Please remember that tomorrow is the deadline for 41.0
tarballs in order to allow release managers sufficient time to prepare
the release.
Thanks for your hard work during this release
On Wed, Sep 1 2021 at 11:00:08 PM +, Release Team
wrote:
Hello all,
We would like to inform you about the following:
* GNOME 41.rc newstable tarballs due
* Hard Code Freeze
Tarballs are due on 2021-09-04 before 23:59 UTC for the GNOME 41.rc
newstable release, which will be delivered
confidence that it is a safe upgrade from earlier
versions of GNOME 40.
Enjoy,
Michael Catanzaro
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
stable release in the GNOME 3 release series. It is succeeded by
GNOME 40.
Michael Catanzaro
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
stable release in the GNOME 3 release series. It is succeeded by
GNOME 40.
Michael Catanzaro
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
On Fri, Mar 19 2021 at 01:33:06 PM +, Javier Jardón
wrote:
GNOME 40.rc is now available. Remember this is the
end of this development cycle; enjoy it as fast as you can, the final
release is scheduled for this coming week! (and It's looking
beautiful)
Please also remember that 40.0
On Sun, Feb 28, 2021 at 11:35 am, Michael Catanzaro
wrote:
And it turned that bad plumbing was at fault
(Turns out bad things happen when drain pipes slope upwards instead of
downwards)
___
desktop-devel-list mailing list
desktop-devel
On Sat, Feb 27, 2021 at 7:42 pm, Bastien Nocera
wrote:
It's like giving your mate a key to your place so they can do laundry
while you're away. You don't expect them to have flooded the place
when
you get back.
In fairness, the one time I flooded a laundry room, I caught it pretty
quickly
FWIW I agree that freeze should apply to tarballs, i.e. any features or
UI changes not in a tarball release by the beta tarball deadline ought
to be delayed until the next release cycle. Dropping major changes a
week later isn't fair to Shaun and anyone else working on
documentation. But
On Thu, Jan 14, 2021 at 11:04 am, Bastien Nocera
wrote:
I don't think you quite understand just how much trust was lost when a
member of the release team can't follow the goals we set ourselves as
a
project.
You broke that trust, then bumbled into breaking it again, fixed the
code, but never
On Thu, Jan 14, 2021 at 5:13 pm, Jordan Petridis
wrote:
There's also c) include a temporary patch in gnome-build-meta till
the MR is merged,
though git will complain about the patch being already applied once
merged and break
the build.
There's also d) pin the module to your branch/fork of
On Thu, Jan 14, 2021 at 11:04 am, Bastien Nocera
wrote:
I don't think you quite understand just how much trust was lost when a
member of the release team can't follow the goals we set ourselves as
a
project.
You broke that trust, then bumbled into breaking it again, fixed the
code, but
On Thu, Jan 14, 2021 at 11:04 am, Philip Withnall
wrote:
I don’t know anything about what the release team is doing with all
these modules, or why, but perhaps rather than the default being
“pull
in all the modules into an OS build and urgently push fixes to the
modules if something
On Thu, Jan 14, 2021 at 12:16 pm, Jonas Ådahl wrote:
FWIW, mutter and gnome-shell (and others too I suspect) only allow
maintainers to merge to master (due to a lack of better granularity in
the community edition of GitLab), but that is primarily due to us
using
marge-bot, so while
On Wed, Jan 13, 2021 at 9:28 pm, Philip Withnall
wrote:
Given that you’ve just committed to submitting MRs and waiting for
CI
to pass, rather than pushing directly to master, perhaps this rule
should be rethought?
Hm... as long as we have permission to merge the MR after CI has
passed, or
On Wed, Jan 13, 2021 at 7:53 pm, Bastien Nocera
wrote:
> "I need to remember not to [push commits directly to the main branch]
> for your modules, sorry"
I was trying to be sincere, not dismissive:
mcatanzaro: "I need to remember not to for your modules, sorry"
"Can hardly complain about
Hi,
Yesterday, after I committed the typo to Calendar, I promised to use
merge requests from now on when committing build fixes. Previously, I
had promised to do this only for your projects, but yesterday I forgot,
and not for the first time. I understand that's frustrating. From now
on,
On Tue, Jan 12, 2021 at 9:31 am, Michael Catanzaro
wrote:
We've had at least four separate breakages from four separate projects
Make that seven breakages from six projects. Thanks to everyone who
helped with getting these back under control. With a little luck, maybe
we'll get a successful
Hi developers,
Please remember that action is required when updating your dependencies
or build options. You need to either make sure gnome-build-meta is OK
with your changes, or ask release team to investigate on your behalf.
We've had at least four separate breakages from four separate
On Fri, Jan 8, 2021 at 11:30 am, Michael Catanzaro
wrote:
We have a fix that I think is ready, but not yet deployed. The
tarball deadline for 40.alpha tarballs will be extended until at
least Monday. (Additional extension may be necessary depending on
when the fix gets deployed.)
OK
On Thu, Jan 7, 2021 at 4:02 pm, Michael Catanzaro
wrote:
We forgot to ensure that ftpadmin is compatible with the new
versioning scheme. In short, it's not. So you cannot actually make
40.alpha releases yet. Please hold off on 40.alpha until further
notice. We'll figure this out. :)
We have
Hi maintainers,
We forgot to ensure that ftpadmin is compatible with the new versioning
scheme. In short, it's not. So you cannot actually make 40.alpha
releases yet. Please hold off on 40.alpha until further notice. We'll
figure this out. :)
GNOME 3.38.3 and 3.36.9 can proceed as planned,
are now beginning work on our next release, GNOME 40, which
will be released in March. Until then, enjoy GNOME 3.38.
Michael Catanzaro
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop
are now beginning work on our next release, GNOME 40, which
will be released in March. Until then, enjoy GNOME 3.38.
Michael Catanzaro
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop
Hi,
We have been trialing Discourse as a potential replacement for GNOME
mailing lists in order to modernize our communications infrastructure
and make contributing to GNOME more attractive to newcomers. If this
goes well, then we should be able to shut down most of our antiquated
mailing
I'll look into what's wrong with this automated mail. It's trying to
tell you that the soft translation deadline is Wednesday, September 9.
In order to give translators time to fully translate GNOME 3.38, please
don't release 3.38.0 tarballs until Thursday this week. (Reminder:
tarballs are
Hi devs,
Please remember that hard code freeze is starting in just under two
hours. If you need to break the freeze to improve the quality of GNOME
3.38, please report an issue at our new freeze break tracker:
https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues
Michael
Hi,
GNOME 3.37.91 is now available! This is the second beta release of
GNOME 3.37. Please note: we are now in string freeze, so be kind to
translators and stop changing strings! :)
The corresponding flatpak runtimes have been published to Flathub. If
you'd like to target the GNOME 3.38
Hi,
We're planning to turn off the release team mailing list. That means
sending freeze break requests to the mailing list will no longer work.
Instead, you can report issues here to request UI, feature, API, or
hard code freeze break:
On Tue, Aug 4, 2020 at 8:08 am, Michael Catanzaro
wrote:
I'll investigate to see what went wrong when generating the schedule
and get that fixed.
This is fixed.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https
On Tue, Aug 4, 2020 at 8:47 am, Shaun McCance wrote:
Back when we did Monday releases, I rememeber we were asked to wait
until closer to the deadline, to give translators more time. Is that
still the case?
Hi Shaun,
Good question! There's no need to worry about translations except for
the
Hi devs,
Please remember that UI freeze, feature freeze, and API freeze for the
3.38 release begin this Saturday, August 8 at 23:59 UTC. That's also
our tarball deadline for 3.37.90 releases. Please aim to release your
3.37.90 tarballs before then: no need to wait until the deadline.
Hi, this is now fixed.
But somehow, my GitLab notification settings got reset and I've been
missing mails. Be careful! Check your notification settings for the
projects you care about.
Michael
___
desktop-devel-list mailing list
Hi,
If you've just received an email about being removed from GNOME group
due to two years of inactivity, you can follow:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/380
GitLab migration was roughly two years ago, so I hazard to guess that's
probably related.
Happy
Hi,
Several developers are interested in moving away from our confusing
even/odd versioning scheme.
Emmanuele has proposed a new version scheme on Discourse:
https://discourse.gnome.org/t/straw-man-proposal-changing-the-gnome-versioning-scheme/1964/57
It seems possible that GNOME 3.38 might
Hi,
GNOME 3.37.3 is now available. This is our third unstable release
leading to the 3.38 release in September.
If you want to compile GNOME 3.37.3, you can use the official
BuildStream project snapshot:
https://download.gnome.org/teams/releng/3.37.3/gnome-3.37.3.tar.xz
The list of updated
On Thu, Jun 18, 2020 at 5:58 pm, Michael Catanzaro
wrote:
It seems all privileged runners have disappeared. All my glib-net CI
pipelines are stalled. :(
Looks like this was some sort of temporary infrastructure problem last
night, because it's fixed again now
It seems all privileged runners have disappeared. All my glib-net CI
pipelines are stalled. :(
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Good questions! Under flatpak, WebKit will actually use flatpak-spawn
to create a flatpak subsandbox, instead of using its own bubblewrap
sandbox. So yes, WebKit's bubblewrap sandbox does not get used, but
there is a flatpak "subsandbox" instead. It effectively does:
$ flatpak-spawn
Hi,
Please help GNOME sandbox all its uses of WebKit! We're about halfway
done:
https://gitlab.gnome.org/GNOME/Initiatives/-/issues/19
If you maintain an application using WebKit that hasn't yet enabled the
sandbox, it usually only requires one or two lines of code.
Applications that use a
On Sun, Jun 14, 2020 at 1:42 pm, philip.chime...@gmail.com wrote:
Is GJS really the only project that tests merge requests using ASan
and LSan? If not, please speak up so we can have a better idea of how
many projects are affected.
No, glib-networking also requires asan for every merge
On Sun, May 31, 2020 at 8:14 pm, Bartłomiej Piotrowski
wrote:
Previously uploaded cache was still being used. Jobs reliably pass
now,
or fail for reasons unrelated to infrastructure.
The infrastructure seems to be fixed now, thanks!
___
3.34
and 3.36 runtimes out soon for flatpak users.
On Mon, Jun 1, 2020 at 9:03 am, Michael Catanzaro
wrote:
Hi distributors,
By now, you're likely to already have at least one bug report about
this, but an important root CA expired yesterday, leading to a large
number of certificate
On Sun, May 31, 2020 at 11:35 am, Michael Catanzaro
wrote:
Still failing, now on a different runner:
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/744761
Can you please try triggering a new CI run to make sure it actually
passes...?
I just triggered seven pipelines and five of them failed
On Sun, May 31, 2020 at 5:43 pm, Bartłomiej Piotrowski
wrote:
I don't see a good explanation why this particular runner is unhappy
at
this point. Distributed and local cache are disabled and some flatpak
jobs pass just fine. I paused it for now.
Still failing, now on a different runner:
It's still broken as of right now, see e.g.
https://gitlab.gnome.org/Vanadiae/epiphany/-/jobs/744498
Or:
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/744499
Or:
https://gitlab.gnome.org/jbrummer/epiphany/-/jobs/744537
It seems like nearly 100% of jobs are still failing. :(
On Thu, May 28, 2020 at 7:46 pm, Zander Brown wrote:
Good luck sysadmining, sure it'll all be fine
So I also thought this would be low-risk maintenance, but half our CI
runs are still failing and that halts development on projects that
require successful CI. Definitely not a good situation
Looks like CI jobs are now failing when trying to download from GitLab
registry:
https://gitlab.gnome.org/GNOME/gnome-robots/-/jobs/741566
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
On Wed, Apr 29, 2020 at 8:16 pm, Tres Finocchiaro via
desktop-devel-list wrote:
As an aside -- as a Java developer, I've personally never forced the
Gtk theme in my applications -- because back when I used KDE the Gtk
theming wasn't very good. From the comments above it sounds like the
On Thu, Apr 30, 2020 at 2:33 pm, Simon McVittie via desktop-devel-list
wrote:
Debian's gnome-session package carries a patch to revert that commit,
unfortunately. We'd like to stop doing that, but as you say, there are
at least 225 instances of packages doing it wrong.
Only way to guarantee
Hi,
GNOME 3.34.6 is now available. This is our second "oldstable" release,
intended to benefit distributions that have not yet upgraded to GNOME
3.36, and also flatpak applications that are still using the 3.34
runtime.
If you want to compile GNOME 3.34.6, you can use the official
On Thu, Apr 2, 2020 at 11:13 pm, Florian Müllner
wrote:
Is it just me or are the April 25th releases missing?
Definitely just you... they're in there! Just tested adding it in
Evolution.
This URL should work in GNOME Calendar:
https://www.gnome.org/start/unstable/schedule.ics
/NEWS
The source packages are available here:
https://download.gnome.org/core/3.36/3.36.1/sources/
Best wishes,
Michael Catanzaro
GNOME Release Team
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo
On Thu, Mar 26, 2020 at 10:59 am, Milan Crha via desktop-devel-list
wrote:
I also moved to release on
Friday, instead of Monday (weekend is out of question here),
Tarballs are always due on Saturday. We don't have Monday deadlines
anymore.
I agree the timing is pretty unfortunate. I guess
On Sat, Mar 21, 2020 at 1:21 pm, Christian Hergert
wrote:
Those words sound incompatible to me in the same way that if you have
access to Linux's perf, you can sniff pretty much any data you want on
the system.
We're talking about CI runners... we only need privileged access inside
the
On Fri, Mar 20, 2020 at 8:20 pm, philip.chime...@gmail.com wrote:
Has anyone managed to get lsan/asan to work without CAP_SYS_PTRACE
yet or otherwise have any suggestions on what would need to be done
to support it in an unprivileged setup?
I marked my CI as privileged:
On Thu, Mar 19, 2020 at 8:23 am, Milan Crha via desktop-devel-list
wrote:
My question is: is there anything one can do to get to those bits, or
it's just a lost battle? Maybe, could the .Debug be split into smaller
parts, thus it's bearable when the download fails (due to the server
error)?
Hi,
Our automated reminder is experiencing technical difficulties at the
moment, so here's your heads-up that 3.36.0 tarballs are due this
Saturday, March 7 by 23:59 UTC. The translation deadline for 3.36 was
yesterday, so now is a great time to release your 3.36.0 tarball.
Thanks for all
On Mon, Mar 2, 2020 at 9:41 pm, Philip Chimento via desktop-devel-list
wrote:
Also, has anyone successfully gotten a CI job that uses lsan or asan
to work in the unprivileged setup? (See my previous question about
CAP_SYS_PTRACE.)
Hm, looks like my glib-networking CI is broken due to this. I
On Mon, Feb 24, 2020 at 6:46 pm, Jordan Petridis via desktop-devel-list
wrote:
No there isn't, it was working properly when it was first rolled out.
I've started seen this issue today and looks like it only affecting
some runners, so I am guessing something got updated or new runners
where
On Fri, Feb 28, 2020 at 10:25 am, Mart Raudsepp wrote:
This sounds more like a "problem" with the distribution, not that such
releases shouldn't happen.
If a minor release upgrade prompts for a full system reboot, then
maybe
that update shouldn't be packaged up on such distros - it shouldn't
On Wed, Feb 26, 2020 at 3:39 pm, Michael Catanzaro
wrote:
Schedule:
* Saturday, Feb 29: 3.35.92 tarball deadline and hard code freeze
* Saturday, March 7: 3.36.0 tarball deadline
* Wednesday, March 11: GNOME 3.36.0 release day
Another important date is Wednesday, March 4. For the first time
On Wed, Feb 19, 2020 at 5:51 pm, Iain Lane
wrote:
any thoughts on why we might have quality
issues with .0 releases or is it really mostly about the schedule?
I don't think it's *mostly* about schedule... it's mostly about lack of
upstream QA. But schedule plays a significant role, too,
Hi,
Just a reminder that we are getting very close to GNOME 3.36 [1]!
The tarball deadline for 3.35.92 is Saturday at midnight (UTC). If you
release on weekdays, please be sure to release either Thursday
(tomorrow) or Friday. Normally we have a bunch of late releases on
Monday and Tuesday;
On Mon, Feb 24, 2020 at 11:08 am, Michael Catanzaro
wrote:
I have two failed builds on flatpak-gcc176 (also broken) and two
failed builds on flatpak-gcc150.fsffrance.org (also broken). My plan
is to keep retrying until I get flatpak-progress again. I need a
successful build urgently because
On Mon, Feb 24, 2020 at 4:48 pm, Bastien Nocera
wrote:
Ran it 3 separate times, on 3 different runners, to no avail.
I'm struggling with this currently.
From yesterday:
https://gitlab.gnome.org/GNOME/epiphany/pipelines/10/builds
I have a failed build on flatpak-gcc175 (broken), then a
On Mon, Feb 24, 2020 at 10:11 am, Bastien Nocera
wrote:
It uses the flatpak_ci_initiative.yml template and throws this error:
bwrap: Creating new namespace failed, likely because the kernel does
not support user namespaces. bwrap must be installed setuid on such
systems.
I'm seeing this
On Thu, Feb 20, 2020 at 12:00 pm, Alexandre Franke
wrote:
Once you reach a decision on that term, can you please explain the
change on the i18n list so that coordinators know what branches are
worth working on?
I believe we had decided on 12 months.
That said, it shouldn't affect translators
On Thu, Feb 20, 2020 at 10:26 am, Isaque Galdino
wrote:
Where do I find instructions to do so?
Thanks.
Hi, see:
https://wiki.gnome.org/Newcomers/BuildSystemComponent
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
On Wed, Feb 19, 2020 at 8:00 pm, Sam Thursfield
wrote:
We've been using podman successfully to build the Tracker CI images.
The exact build instructions are here:
https://gitlab.gnome.org/GNOME/tracker-oci-images/blob/master/.gitlab-ci.yml
These containers are working fine in GitLab CI,
On Wed, Feb 19, 2020 at 11:57 am, Matthias Clasen via release-team
wrote:
There next (and last) stable 3.34 update is planned for end of
March, see https://wiki.gnome.org/ThreePointThirtyfive
Small correction: we're going to be doing something new and continuing
3.34 releases through the
On Wed, Feb 19, 2020 at 2:50 pm, Bartłomiej Piotrowski
wrote:
If your project's pipeline is using Docker to build an image from
Dockerfile, consider switching to podman or buildah as they should
work
unprivileged.
Have you tested this? I've tried many times and afaik GitLab is simply
Hi,
GNOME 3.35.91 is now available! This is the second beta release of
GNOME 3.36.
Please note: we are now in string freeze, so be kind to translators and
stop changing strings.
The corresponding flatpak runtimes have been published to Flathub. If
you'd like to target the GNOME 3.36
On Wed, Feb 12, 2020 at 4:35 pm, Michael Catanzaro
wrote:
Here is my suggestion: fellow Matrix proponents, let's turn off the
IRC bridge ASAP. All we've accomplished by running the IRC bridge is
convincing GNOME devs that Matrix is awful. I'm pretty sure that all
of this negative feedback
On Thu, Feb 13, 2020 at 11:52 pm, Matthew Hodgson via
desktop-devel-list wrote:
1. The original issue that Michael Catanzaro reported (Matrix->IRC PM
going missing) was a legitimate bug in the bridge. The bridge is
meant to display an error if you try to talk to an absent IRC u
Hi,
We're going to release GNOME 3.35.91 next week. (Tarball deadline is
Saturday! Please release your tarballs now!) Only problem is, nobody is
really testing 3.35.90 yet, defeating the purpose of having the beta
release.
A couple years ago, we've pushed our releases earlier just a bit
On Wed, Feb 12, 2020 at 4:15 pm, Britt Yazel wrote:
Attached is an image of the compact mode + dark theme. Just for the
record.
The thing is, it really comes down to personal preference. I suspect we
have a lot of people who like web clients, and a lot of people who just
don't. With open
On Thu, Feb 13, 2020 at 11:14 am, Benjamin Berg
wrote:
One could do this comparison properly. But it would need setting up a
private Matrix server for GNOME (possibly without Federation) and then
checking how well it holds up when compared to Rocket.Chat.
gnome.modular.im is already our
On Wed, Feb 12, 2020 at 2:09 pm, Britt Yazel wrote:
I have had horrible experiences with Matrix/Riot.im. I'm not sure
which of those is due to the IRC bridge or which is due to Matrix
itself, or which is due to the clients, but I really shouldn't 'have'
to know the chat system at that level.
On Wed, Feb 12, 2020 at 4:23 pm, Georges Basile Stavracas Neto via
desktop-devel-list wrote:
The Riot application is hard to use. It took me days to figure out
how to connect
to a GNOME room. It doesn't allow me to log out of the servers.
These are all problems with the IRC bridge, not with
On Wed, Feb 12, 2020 at 7:07 pm, Zander Brown wrote:
My concern would be the "federal" nature of matrix where people don't
need a
gnome.org specific chat account to join a room. Whilst there are a
lot of
arguments for this I'm increasingly convinced it's an anti-feature
especially
if we want
1 - 100 of 383 matches
Mail list logo
