2011-09-15 meeting minutes
- From: Frederic Peters <fpeters gnome org>
- To: release-team gnome org
- Subject: 2011-09-15 meeting minutes
- Date: Fri, 16 Sep 2011 09:03:36 +0200
Release Team Meeting, 2011-09-15, 18h UTC
Alejandro Piñeiro Iglesias (API)
Andre Klapper (andre)
Frédéric Péters (fredp)
Olav Vitters (bkor)
Colin Walters (walters)
Matthias Clasen (mclasen)
Javier Jardón (jjardon)
Kjartan Maraas (kmaraas)
Luca Ferretti (elleuca)
- 3.2 status, blockers
- Release-notes writing progress (andre/bkor)
- GNOME Goals, how do they get an official stamp? (andre)
- 3.4 feature proposal period kick off (andre)
- Distributor survey (bkor)
- Maintainer survey (bkor)
- Meeting at Montreal Summit? (fredp)
3.2 status, blockers
Highlights noted by mclasen are:
- login screen needs some patches to land
- osk configuration still needs to land
- contacts experience needs a bit of love all over the place
No real blockers are expected.
Release-notes writing progress
They are ready, proof-reading is welcomed, a note about GNOME online
accounts being an extensible platform will be added, they will be sent
for translation in a few days.
GNOME Goals, how do they get an official stamp?
We should have more goals marked as officials.
The process would be to have goals gathering some feedback on
desktop-devel-list, then the release team would decide in a meeting
(or by email).
For some infrastructure change where patches are trivials it may be
possible to have one person Just Doing It across the modules.
Ideally goals get their own automated report pages, to avoid the
burden of manually maintaining huge tables in live.gnome.org.
3.4 feature proposal period kick off
A feature is an idea that would be a major user visible (and
marketable) change, typically affects several modules, need some
consensus, and a person to lead the change.
The process would be a discussion of the idea on desktop-devel-list,
to achieve a general consensus, the release team role is then to
ensure that a conclusion is reached.
Once agreed, we shouldn't add too much overhead to the process, but it
would definitely be useful to do regular status updates on features.
bkor will prepare a simple survey, to ask for potential issues, check
what they think of GNOME at the moment, and remind them of the
existence of distributors-list.
Addressed to maintainers (it's easy to get them from .doap files), to
get their feeling about 3.2.0, the 3.1 cycle, and provide other
general feedback to the r-t.
The survey would be a few weeks after 3.2.0
Meeting at Montreal Summit?
It will just be mclasen, walters, and fredp, not enough for a real
[AI] fredp to create an automated report on dist-xz usage.
[AI] andre to work on 3.3 schedule
[AI] andre to do another "3.2 blockers" email
[AI] bkor to send a draft distributor survey
[AI] bkor to send a draft maintainer survey
] [Thread Prev