Olav Vitters | 5 Feb 09:56 2010

support@...

There are various ways to contact the sysadmin team

1. Bugzilla
   For specific issues that should be fixed. Bugs can be hidden if
   needed. Not for meant for discussions!
   https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin
2. gnome-infrastructure@...
   Public mailing list. For public discussions. Also receives a copy of
   the publicly visible sysadmin bugs.
   http://mail.gnome.org/mailman/listinfo/gnome-infrastructure
3. gnome-sysadmin@...
   Private mailing list. This receives a *lot* of log output as well;
   not every email might be read.

The following has been discontinued:
4. support@...,
helpdesk@..., etc
   Uses Request Tracker 3 on the background. Receives loads of spam and
   non-sysadmin related requests (distribution problems, jhbuild, etc).

Instead of support@..., use one of the 3 options given above.
Bugzilla is preferred for specific issues, after that
gnome-infrastructure, lastly gnome-sysadmin.

Note:
accounts@... is still active.

--

-- 
Regards,
Olav
(Continue reading)

Matthias Clasen | 5 Feb 14:42 2010
Picon

GNOME 2.29.90 beta tarballs due

Another week, another release ! 2.29.90 tarballs are due next Monday.
Be aware that we are entering UI freeze territory now.

Tarballs are due on 2010-02-08 before 23:59 UTC for the GNOME 2.29.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 2.29.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!

No UI changes may be made at all without confirmation from the release
team and notification to the documentation team.

For more information about 2.29, the full schedule, the official
module lists and the proposed module lists, please see our colorful
2.29 page:
  http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
  http://live.gnome.org/Schedule

Thanks,

Matthias
Matthias Clasen | 11 Feb 07:17 2010
Picon

GNOME 2.29.90 Development Release

This is the first beta release release towards 2.30, which will happen
in March;
time flies. Please try this release and report your findings, so that
we can make
2.30 smooth and polished.

Please note that this milestone marks the beginning of the UI freeze. This is a
good time to start summarizing what has changed in your modules in this cycle,
so that people can work on the release notes! See
http://live.gnome.org/TwoPointTwentynine/ReleaseNotes

Also don't forget we are in those periods:

 * Feature Freeze: new functionality should be completed.
 * String Change Announcement Period: string changes must be announced
  to gnome-doc-list and gnome-i18n.

To compile GNOME 2.29.90, you can the jhbuild [1] modulesets [2] (which
use the exact tarball versions from the official release):

 [1] http://library.gnome.org/devel/jhbuild/
 [2] http://download.gnome.org/teams/releng/2.29.90/

The release notes that describe the changes between 2.29.6 and 2.29.90
can be found here:

platform - http://download.gnome.org/platform/2.29/2.29.90/NEWS
desktop  - http://download.gnome.org/desktop/2.29/2.29.90/NEWS
admin    - http://download.gnome.org/admin/2.29/2.29.90/NEWS
bindings - http://download.gnome.org/bindings/2.29/2.29.90/NEWS
(Continue reading)

Andre Klapper | 17 Feb 21:44 2010
Picon
Picon

Propose new modules for inclusion in GNOME 3.0

Like every 6 months the period for proposing new modules for official
inclusion in GNOME has started.

If you are a maintainer, now is the time to propose your module to be
included in GNOME!

How should you proceed? It's easy, all the information is on:
    http://live.gnome.org/ReleasePlanning/ModuleProposing

The new modules proposal period will most likely end at the beginning of
May 2010 (sorry, the schedule for 2.31/3.0 is not yet ready).

We expect discussion to heat up about those proposals around that
time and to reach a decision by middle of May.

Also note that *early* feedback & testing help maintainers/developers to
work on the issues found (we want them to be fixed at the module
acceptance stage).

As written before, the schedule for 2.31 has not been released yet.
For the official module lists of 2.29, please see our 2.29 page on the
wiki:
    http://live.gnome.org/TwoPointTwentynine

For a quick overview of the GNOME schedule, please see:
    http://live.gnome.org/Schedule

--

-- 
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper
(Continue reading)

Frederic Peters | 19 Feb 11:07 2010
Picon

TARBALLS DUE: GNOME 2.29.91 beta (and string freeze!)

Hello all,

We all want to enjoy GNOME 2.29.91 next week, so the release team will
be waiting for your tarballs!

  Tarballs are due on 2010-02-22 before 23:59 UTC for the GNOME
  2.29.91 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 2.29.91. 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!

Also we enter string freeze on February 24th, no string changes may be
made without confirmation from the translation team (gnome-i18n <at> ) and
notification to release team, translation team, and documentation
team.

From this point, developers can concentrate on stability and
bug-fixing. Translators can work without worrying that the original
English strings will change, and documentation writers can take
accurate screenshots. For the string freezes explained, and to see
which kind of changes are not covered by freeze rules, check
http://live.gnome.org/TranslationProject/HandlingStringFreezes.

And don't forget UI freeze is already in effect: no UI changes may be
made at all without confirmation from the release team and
notification to the documentation team (gnome-doc-list <at> ).
(Continue reading)

Frederic Peters | 24 Feb 17:02 2010
Picon

GNOME 2.29.91 beta released!

Hello all,

Wow! The snow finally melt and there is a timid but still bright sun
illuminating my desktop. That's my *physical* desktop, and it's nice
but even nicer is my *computer* desktop, there is a new GNOME on it!
It is 2.29.91! I am so happy, this is our beta release, be sure to
give it a try!

With this release we are now string frozen, no string changes may be
made without confirmation from the l10n team (gnome-i18n <at> ) and
notification to both the release team and the GNOME Documentation
Project (gnome-doc-list <at> ). The other freezes are of course still in
place, details on http://live.gnome.org/ReleasePlanning/Freezes

To compile GNOME 2.29.91, you can use the jhbuild [1] modulesets
published by the release team [2] (which use the exact tarball versions
from the official release).

 [1] http://library.gnome.org/devel/jhbuild/
 [2] http://download.gnome.org/teams/releng/2.29.91/

The release notes that describe the changes between 2.29.90 and 2.29.91
are available. Go read them to learn all the goodness of this release:

platform - http://download.gnome.org/platform/2.29/2.29.91/NEWS
desktop  - http://download.gnome.org/desktop/2.29/2.29.91/NEWS
admin    - http://download.gnome.org/admin/2.29/2.29.91/NEWS
bindings - http://download.gnome.org/bindings/2.29/2.29.91/NEWS
devtools - http://download.gnome.org/devtools/2.29/2.29.91/NEWS
mobile   - http://download.gnome.org/mobile/2.29/2.29.91/NEWS
(Continue reading)


Gmane