GNOME 3.13.90 releases

Hi all,

In the course of packaging up GNOME 3.13.90, I was advised to switch to
webkit2gtk-4.0 (version 2.5.x) as the new epiphany browser would be
making use of this.

So I jumped into the trouble, adjusted all the packages that depended on
webkit2gtk-3.0 (I try to keep the number of variations low if possible)
and basically everything is set...

BASICALLY: up to this date, there hasn't been a single epiphany release
in the 3.13.x cycle. Is this still going to happen? Or are we no longer
supposed to package epiphany for distributions? :) I'm sure it's just an
oversight, but it happened in all 3.13.x releases so far.

Looking forward to get a release of epiphany 3.13.90 to showcase to our

Dominique / DimStar

Dimstar / Dominique Leuenberger <dimstar <at>>
Ross Lagerwall | 22 Aug 20:59 2014

Stable release policy


Is there any policy about releasing updates to stable branches beyond
the .1 release or is it simply up to each project?  I couldn't find this
info anywhere on the wiki...


Ross Lagerwall
Allan Day | 22 Aug 09:47 2014

GNOME HIG: Feedback Wanted

Hi all,

A new version of the HIG is in the works, to be released along with
GNOME 3.14 [1]. I'm currently looking for feedback.

I'm particularly interested to know if anything is missing, confusing,
or incorrect from a technical point of view (like if any of the
recommendations are impossible or very difficult to do with current

To read the latest version, just clone gnome-devel-docs and open
hig3/C/ with Yelp.



Bastien Nocera | 21 Aug 12:50 2014

gnome-screensaver closed for new bugs


After triaging all the open gnome-screensaver bugs, we closed
for new bugs[1]. gnome-screensaver is not used in GNOME at all since
GNOME 3.8, and
isn't used in recent versions of Unity either.

Users should still be able to get help about it from their distributors.


Frederic Peters | 20 Aug 22:51 2014

GNOME 3.13.90, first beta release!

Hello all,

This is the end of summer, we all got back home after GUADEC, happy
and exhausted, we polished patches and merged branches, and here we
are, with a new release out, and what a release!, it's 3.13.90, the
first beta release of this cycle.

It's full of niceties. Lookup the time of any place in the world
directly from a shell search thanks to Clocks new search provider.
Watch Boxes install a Debian VM all automatically (this is thanks to
Lasse Schuirmann, and the occasion to thank all GSOC students!). Or
simply spend the evening playing a new game, Hitori.

To compile GNOME 3.13.90, you can use the jhbuild modulesets published
by the release team (which use the exact tarball versions from the
official release):

The release notes that describe the changes between 3.13.4 and 3.13.90
are available. Go read them to learn what's new in this release:

  core -
  apps -

The GNOME 3.13.90 release itself is available here:

  core sources -
  apps sources -
(Continue reading)

Release Team | 15 Aug 02:00 2014

GNOME 3.13.90 beta tarballs due (and more)

Hello all,

We would like to inform you about the following:
* GNOME 3.13.90 beta tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of release notes begins

Tarballs are due on 2014-08-18 before 23:59 UTC for the GNOME 3.13.90
beta release, which will be delivered on Wednesday. Modules which were
proposed for inclusion should try to follow the unstable schedule so
everyone can test them.  Please make sure that your tarballs will be
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.13.90. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

New APIs must be fully documented

Writing of release notes begins

For more information about 3.13, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.13

For a quick overview of the GNOME schedule, please see:

(Continue reading)

Andrea Veri | 14 Aug 14:39 2014

Mass Reboot: Sunday 17th of August, 21.30 - 23.00 CET


we'll be performing a mass reboot of all our machines this upcoming sunday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward.

Have an awesome day and thanks for your attention!




Debian Developer,
Fedora / EPEL packager,
GNOME Infrastructure Team Coordinator,
GNOME Foundation Board of Directors member,
GNOME Foundation Membership & Elections Committee Chairman

desktop-devel-list mailing list
desktop-devel-list <at>
Allan Day | 14 Aug 13:23 2014

3.14 Release Notes

Hi everyone!

The 3.14 release is approaching fast, and UI freeze is almost upon us.
Now is a good time to start thinking about the Release Notes.

Please add any features you have worked on over this cycle to the wiki page:

They can be big or small improvements - it doesn't matter.


Sébastien Wilmet | 5 Aug 14:30 2014

Visual effects


I've tried recently KDE, and by default it has too much visual effects,
IMHO. With time, it seems that GNOME follows the same path, there are
more and more visual effects.

I think too much visual effects is bad for a distraction-free desktop.
Exactly the same principle applies for presentation slides. To take an
extreme example, it's not really a good idea to add a firework animation
between each slide… The public will be less concentrated on the contents
of the presentation. On a desktop you want to focus on the work you're
working on.

If more and more visual effects are added to GNOME, and if at one point
we realize (too late) that it's too much, removing lots of visual
effects for the next release will be seen as a regression, and it'll be
much harder to explain to users.

The recent example that I have in mind is the background fading when
selecting a row in a GtkTreeView (and for GtkListBox too I think). It's
really a small detail: when a row is deselected, the background color
goes from blue to white with a progressive fading. And inversely when
you select a row. Now try the following steps, I think you will be
slightly distracted by the background fading of the *deselected* row:

1. Select a row in the list, if not already done.
2. You're searching another item in the list, so you read each item one
by one, until you find what you're searching for (if there is no search
3. Your eyes are focused on the new row you want to select, and you
select that row!
4. If the previous selected row is still visible on the screen, you'll
be slightly distracted by the background fading of the row being

Does that make sense? I know it's really a small detail, but when
updating gtk+ recently and seeing this for the first time, I thought it
was "too much". In KDE there are probably more evident examples.

Best regards,

desktop-devel-list mailing list
desktop-devel-list <at>
Juan R. Garcia Blanco | 3 Aug 16:41 2014

Announce release of non-official module

Hi all,

I inherited libchamplainmm some time ago now. libchamplainmm, as you
suppose, are the C++ bindings for libchamplain. I've been working on it
to make it up to date with upstream libchamplain.

I think libchamplainmm is now quite complete. I'd like to make a
development/unstable release; i.e. create a tag and announce it. I don't
even want to push a tarball to gnome's ftp. But I would like to send an
'official' announcement to gnome-announce-list mainly to advertise the
project; probably not many people knows that C++ bindings exist.

So my question is: could I send an announcement to gnome-announce-list
without submitting a tarball, just tagging the repo?

Thank you very much.

Best regards,
Olav Vitters | 3 Aug 01:33 2014
Picon changes and new doap file requirements

 [ Please reply to desktop-devel-list <at> ]

André Klapper suggested we should make more use of the doap files. As a
result of that together with GUADEC, the following changes have been
made on

1. New categories: Core, Core Apps, Apps
   Note: Not every module has been put into right category. If you spot
   errors, please let release-team <at> know. I'm planning to add
   some cross checks in the release team scripts to ensure everything
   is and stays aligned.

2. "Owner" field shows programming language
   This is taken from the programming-language field in the doap file.
   You can specify multiple programming languages. Piotr Drąg and André
   Klapper ensured that most Core/Core Apps/Apps modules have these
   fields. This should make it easier for someone to suggest a good up
   to date overview of modules to start off with.
   Note: Unfortunately cannot rename the "Owner field" into programming
   language ☹

3. Stats per week/month/quarter/year
   e.g. Matthias Clasen apparently does most gtk+ commits.

To ensure that the doap file can be used for more purposes, the
following additional fields are now mandatory for Core/Core Apps/Apps

- programming-language
- description

DOAP files are only checked when you change them. Changes are reflected
almost immediately.

For the full details behind these DOAP files, see:

Aside from above I also slightly changed the header
(e.g. shows RecentChanges+Schedule again). The Schedule is IMO quite

desktop-devel-list mailing list
desktop-devel-list <at>