From: guixest <guixest@protonmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: "guix-devel\\@gnu.org" <guix-devel@gnu.org>
Subject: Re: DE
Date: Thu, 10 Oct 2019 04:59:01 +0000 [thread overview]
Message-ID: <S4KupQSh7vW4jUmE613vSu32GY_HyLb9smU-atmE42-hX5tICzl0UXd5BcY1G6LRer41DszXJPWpJneOTH6SPy9BQ_MBxNg1tZbave2g-UM=__33695.5983935454$1570690094$gmane$org@protonmail.com> (raw)
In-Reply-To: <87zhi9qogi.fsf@ngyro.com>
thanks.
I understand the process you explained. Btw, when is the next batch coming?
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, October 10, 2019 3:17 AM, Timothy Sample <samplet@ngyro.com> wrote:
> Hi guixest,
>
> guixest guixest@protonmail.com writes:
>
> > hi.
> > I was looking at available gtk based desktops. It appears xfce is up to date where as gnome
> > is not. is there a reason for this?
>
> Yes and no. As I understand it, upgrading GNOME often means upgrading
> GTK and GLib, which have a lot of dependants. We batch those kinds of
> upgrades because the build farm needs time to catch up, and we need to
> test the resulting package set. Usually this happens a couple times a
> year, but the last batch took closer to a whole year to get through. (A
> million thanks to everyone who worked so hard to get through it!)
>
> Beyond that, having helped test two GNOME upgrades, I can say that there
> are enough issues that it is a bit of a “project”. It’s not so simple
> as just bumping the versions and building the packages.
>
> That being said, I am hopeful that we will eventually be able to catch
> up to upstream. We have some code for version 3.32, which is the
> next-to-latest version. If someone (me if I can find the time) gets it
> cleaned up quick enough, it will be part of the next batch upgrade.
> BTW, we always appreciate help with testing if you’re up for it. :)
>
> -- Tim
prev parent reply other threads:[~2019-10-10 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 2:56 DE guixest
2019-10-10 3:17 ` DE Timothy Sample
2019-10-10 4:59 ` DE guixest
2019-10-10 13:23 ` DE Timothy Sample
2019-10-10 4:59 ` guixest [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='S4KupQSh7vW4jUmE613vSu32GY_HyLb9smU-atmE42-hX5tICzl0UXd5BcY1G6LRer41DszXJPWpJneOTH6SPy9BQ_MBxNg1tZbave2g-UM=__33695.5983935454$1570690094$gmane$org@protonmail.com' \
--to=guixest@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.