From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev-announce] GNOME team meeting 2017-02-10
Date: Wed, 08 Feb 2017 10:07:07 +0200 [thread overview]
Message-ID: <1486541227.994.8.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
The Gentoo GNOME team will meet on Friday 2017-02-10, 20:00 UTC in the
#gentoo-meetings channel on Freenode.
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170210T20
Agenda:
* GNOME 3.22 stabling status
** Should we revert default session to X11 before stabling even if
USE=wayland is used, as 3.24 is close-by that makes it work better and
some team members themselves are having issues with it on 3.22?
* Do we need an upgrade guide for 3.22?
* -9999 ebuilds in main tree?
* Overlay vs main tree for beta/rc releases
* Overlay vs main tree for early development releases
* Meta packages dependencies and USE flags (gnome, gnome-light, gnome-
core-libs, etc)
* Lead elections (might get deferred to e-mails for a quorom)
* Open floor
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
reply other threads:[~2017-02-08 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1486541227.994.8.camel@gentoo.org \
--to=leio@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox