Nabble - Gnome - Dev - Announce

GNOME 2.29.3 released

2009-12-03T08:39:36Z

GNOME 2.29.3 Development Release
========================

The third development release of GNOME 2.29/2.30 development cycle is here !

To compile GNOME 2.29.3, 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.3/

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

platform - http://download.gnome.org/platform/2.29/2.29.3/NEWS
desktop - http://download.gnome.org/desktop/2.29/2.29.3/NEWS
admin - http://download.gnome.org/admin/2.29/2.29.3/NEWS
bindings - http://download.gnome.org/bindings/2.29/2.29.3/NEWS
devtools - http://download.gnome.org/devtools/2.29/2.29.3/NEWS

The GNOME 2.29.3 release is available here:

platform sources - http://download.gnome.org/platform/2.29/2.29.3/
desktop sources - http://download.gnome.org/desktop/2.29/2.29.3/
admin sources - http://download.gnome.org/admin/2.29/2.29.3/
bindings sources - http://download.gnome.org/bindings/2.29/2.29.3/
devtools sources - http://download.gnome.org/devtools/2.29/2.29.3/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.29, the full schedules, the official
modules list and the proposed modules list, please see our 2.29 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Branch notifications

2009-11-28T14:42:17Z

Hey folks,

Since the migration to git, we now get automatic branch
notification emails to release-team, gnome-doc-list, and
gnome-i18n for any new branch matching "gnome-\d+-\d+".
As such, it is no longer necessary to send notification
emails manually. See the updated MaintainersCorner:

http://live.gnome.org/MaintainersCorner

Thanks to Olav Vitters, the automatic email will now also
be sent to your @gnome.org email alias. This will allow
you to verify the notification was sent by just checking
your own inbox. Please make sure the address for your
@gnome.org alias is correct.

I hope this makes things at least a little bit easier
for maintainers.

--
Shaun

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.29.3 Development Release

2009-11-27T11:52:53Z

Hello all, its that time again:

Tarballs are due on 2009-11-30 before 23:59 UTC for the GNOME 2.29.3
unstable 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.3.
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!

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
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.29.2 Released!

2009-11-18T16:46:56Z

GNOME 2.29.2 Development Release
================================

So, here's the second development release of GNOME 2.29/2.30 development
cycle. I was a bit lazy so this release is a couple hours late. But
we're on time
for certain timezones so I guess this is ok :-P

This release includes the accepted modules proposed for 2.30.

To compile GNOME 2.29.2, 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.2/

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

platform - http://download.gnome.org/platform/2.29/2.29.2/NEWS
desktop - http://download.gnome.org/desktop/2.29/2.29.2/NEWS
admin - http://download.gnome.org/admin/2.29/2.29.2/NEWS
bindings - http://download.gnome.org/bindings/2.29/2.29.2/NEWS
devtools - http://download.gnome.org/devtools/2.29/2.29.2/NEWS

The GNOME 2.29.2 release is available here:

platform sources - http://download.gnome.org/platform/2.29/2.29.2/
desktop sources - http://download.gnome.org/desktop/2.29/2.29.2/
admin sources - http://download.gnome.org/admin/2.29/2.29.2/
bindings sources - http://download.gnome.org/bindings/2.29/2.29.2/
devtools sources - http://download.gnome.org/devtools/2.29/2.29.2/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.29, the full schedules, the official
modules list and the proposed modules list, please see our 2.29 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.29.2 Development Release

2009-11-16T03:15:56Z

Hello all,

Again there is some bot slacking off and this email comes late, but
you know we are back on the development track, enjoying the ride to
3.0 -- with a short stop for 2.30 along the way. New modules have
been accepted, old modules are still kicking ass, they will all get
new releases today, thanks to you.

Tarballs are due on *today*, Monday November 16th, before 23:59 UTC
for the GNOME 2.29.2 Development Release, which will be delivered on
Wednesday. Modules which were proposed for inclusion should try to
follow the 2.29 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.2. 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!

For more informations about 2.29, the full schedule, the official
module lists and the proposed module lists, please see our colorful
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

Cheers,

Frederic
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

New module decisions for 2.30

2009-11-09T13:38:29Z

Hi,

The release team met last week to eat some ice cream, chat about who
will be the villain(s) in the next Batman movie and play some football
(or soccer if you're living in a country where there's another football
game ;-)). We still found some time to discuss the new module proposals.

Many thanks to the people who contributed to the discussion on the list,
and to the authors and maintainers of the proposed modules!

Short summary
=============

Please make sure to read the details for modules that are of interest to
you, as the release team generally comments on why a module is approved
or rejected, with recommendations that we'd like to see followed.

In:
gmime (external dependency)
libdb (external dependency)
vala (external dependency)
gnome-packagekit (desktop)
nautilus-sendto (desktop)

In, but not as expected:
tracker (external dependency instead of desktop)
dconf (not for 2.30, but pre-approved for 3.0)

Blocking on external issues:
clutter-core (see details below)

Out:
couch-db, evolution-couchdb (desktop)
globalmenu (desktop)
nautilus-actions (desktop)

Withdrawn by maintainer:
emerillon (desktop)
libvtemm (desktop)

Details
=======

+ gmime (external dependency)
- needed by totem-pl-parser (in 2.28 already)
- would be needed by tracker
=> approved
=> it would make sense to make evolution-data-server/evolution use
gmime to remove code duplication.

+ libdb (external dependency)
=> already approved by mail

+ vala (external dependency)
- would be needed by parts of dconf and tracker
- gathered quite some interest already
=> approved
=> the release team encourages maintainers of modules using vala to
put generated files in tarballs to enable compilation without vala
being installed.

+ clutter-core (desktop)
- already adopted by the GNOME community
- already an external dependency
- not hosted on GNOME infrastructure, but tarballs and API docs are
now there (missing: git and bugzilla)
- copyright waiver possibly limits contributions:
http://bugzilla.openedhand.com/waiver.html
- copyright assignment is also an issue
=> the release team is working with the Foundation to investigate the
copyright waiver and copyright assignment, and with Intel to find
an appropriate solution.
=> feedback from the community at large on what solution would be
appropriate is welcome.
=> at least bugzilla should be moved to the GNOME infrastructure.
=> rejected, until those (non-technical) issues are solved. We still
support the project as we believe it's really essential for GNOME,
especially in the GNOME 3 context.

+ couch-db, evolution-couchdb (desktop)
- not really used widely at the moment
- it seems the mozilla javascript engine is a highly recommended
dependency. Until we come to a decision about the mozilla vs webkit
engines, this is an issue.
=> rejected: too early for wider adoption.

+ dconf (desktop)
- agreement it's the way forward
- concerns about migration of settings
- concerns about the lack of planning for admin tools (pessulus and
sabayon)
- concerns about the fact that we need stuff in glib but that's not
there yet (although we know there's a plan for this)
- a massive migration from gconf to dconf would be preferrable
(instead of having some modules using gconf and some other modules
using dconf). We know it might not be realistic, though.
=> rejected for this cycle, but pre-approved for the next cycle
(assuming glib gets the required API for the next cycle). The
additional time should be used for careful planning of the above
items.
=> we encourage developers to look at it and to create gsettings
branches for their modules (like devhelp and gedit).

+ emerillon (desktop)
=> withdrawn by maintainer

+ globalmenu (desktop)
- still considered as a hack by platform maintainers
- does not align with the GNOME 3 plans at the moment
=> rejected

+ gnome-packagekit (desktop)
- the PackageKit integration in GNOME offers nice features
- the PackageKit tools are not used widely by all distributions right
now
- some parts of gnome-packagekit have a place in the desktop suite,
but not all of them, so it's not clear what to do right now.
=> approved
=> we believe packagers will only take the parts of gnome-packagekit
they want in their packages anyway. Packagers can contribute
patches to make this easier for them as Richard is open to this
idea.

+ libvtemm (desktop)
=> withdrawn by maintainer

+ nautilus-actions (desktop)
- some think it's mostly targetted at advanced users, and so it's
fine to keep it out of the desktop
- should potentially be integrated in nautilus itself in a
non-intrusive way if possible
=> rejected, but we can give it more visibility as part of our goal
to advertize more GNOME applications

+ nautilus-sendto (desktop)
- widely adopted
- integrates in a non-intrusive way to nautilus
=> approved
=> it might make sense to integrate the feature directly in nautilus
if possible (and have the plugins directly in the applications
themselves)

+ tracker (desktop)
- this is tracker 0.7 (not 0.6)
- mixed feelings in the community
- the tracker team has done some good work recently, and we want to
give a chance to integrate their work
- we need more integration first; right now, it seems to be mostly
integration of the search and not the metadata
- we think applications should not rely on the indexer being enabled,
since people might disable it. This should hopefully already be
fine.
=> approved as external dependency
=> we encourage tracker developers to clearly separate the indexer
from the store to avoid confusion in the mind of non-tracker
developers.

Thanks,

Vincent

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 3.0 in September 2010

2009-11-09T13:35:16Z

GNOME 3.0 will be released in September 2010, and in the meantime, we
will release GNOME 2.30 in March 2010, continuing our long-standing
tradition of six-months releases.

Thanks to the input from the community, we were able to draw a clear
picture of where we stand today and where we will be next March. As
mentioned in the GNOME 3.0 planning document [1], the release date for
3.0 was not set in stone: while we're using a strict schedule that
allows us to release GNOME every six months, GNOME is above all using
quality-based release engineering. That's why our community wants GNOME
3.0 to be fully working for users and why we believe September is more
appropriate.

Note that this release date for 3.0 doesn't mean that 2.30 will be less
stable than usual. On the contrary, this will help us integrate the
changes that are ready for 2.30, while leaving the parts that are still
rough on the edges outside of GNOME, as used daily by our users, until
after 2.30 is out. This will solidify both our 2.30 and 3.0 releases.

The idea of doing GNOME 3.0 was first seriously discussed in 2008,
before focus areas were defined in 2009, alongside a plan to reach
3.0. Those focus areas include revamping the user experience,
streamlining the platform and improving the promotion of GNOME. Compared
to GNOME 3.0, GNOME 2.30 will see the iterative improvements and bug
fixes that people have now come to expect from our 2.x branch, in
addition to some preliminary work needed for GNOME 3.0.

The GNOME 3.0 planning document was answered by the community with a
tremendous amount of work, with various teams taking the opportunity to
set their own goals for 3.0. Such goals range from modernizing part of
our stack to proposing new UI models for our desktop: those broad
changes show our ambition to always offer the best to developers and
users, and this make our path to GNOME 3.0 most exciting!

Let's make 2010 a fantastic year for GNOME!

Vincent

[1] http://live.gnome.org/ThreePointZero/Plan

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Requests for comment sent about the release date for GNOME 3.0

2009-11-03T08:26:14Z

Hi all,

I just sent some mails to various teams to get their input about the
release date of GNOME 3.0. The release team will soon decide the release
date for 3.0, and we expect the input from teams in our community to
help us have a clear picture.

I tried to ping all teams where we know there are plans for 3.0, but in
case I forgot one team (please make me publicly ashamed if this is the
case), here's what was sent, so you can also send your feedback to the
release-team@...:

===========
The release team is gathering comments from various teams to get a
proper idea of which of March or September 2010 is more appropriate for
the release of GNOME 3.0. The decision for the release date is following
what we set in the 3.0 planning document [1]: we want 3.0 to be out in
2010, but we also want to make sure that 3.0 is rock-solid; your input
will help us take an informed decision.

It'd be great if someone could summarize the status of the work that is
being done in your team, and how March or September would work for you.

[1] http://live.gnome.org/ThreePointZero/Plan
===========

(Note: we prefer one-mail summaries to long threads for this ;-))

Thanks,

Vincent

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.29.1 Released!

2009-10-28T16:38:27Z

GNOME 2.29.1 Development Release
================================

We're only a few days after 2.28.1, and 2.29.1 is already there! We have
some brave people who did some amazing work for this release, with new
features in various modules. And of course, the numerous bug fixes that
we're all used to. It's really exciting to already be able to play with
some nifty new features: it announces some great fun during the next few
months. Of course, some tarballs are still in the 2.28 era, but that's
mostly because the tarballs due mail was late (you can blame your
favorite release team member for this -- hopefully, I'm not your
favorite one ;-)).

Oh, and with the release team meeting this week-end for new module
decisions, it means 2.29.2 will surely be full of awesomeness brought by
new modules. To make this a good ride, we should make sure the old
modules offer some competition to the new code, with great changes for
users everywhere!

To compile GNOME 2.29.1, 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.1/

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

platform - http://download.gnome.org/platform/2.29/2.29.1/NEWS
desktop - http://download.gnome.org/desktop/2.29/2.29.1/NEWS
admin - http://download.gnome.org/admin/2.29/2.29.1/NEWS
bindings - http://download.gnome.org/bindings/2.29/2.29.1/NEWS
devtools - http://download.gnome.org/devtools/2.29/2.29.1/NEWS

The GNOME 2.29.1 release is available here:

platform sources - http://download.gnome.org/platform/2.29/2.29.1/
desktop sources - http://download.gnome.org/desktop/2.29/2.29.1/
admin sources - http://download.gnome.org/admin/2.29/2.29.1/
bindings sources - http://download.gnome.org/bindings/2.29/2.29.1/
devtools sources - http://download.gnome.org/devtools/2.29/2.29.1/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.29, the full schedules, the official
modules list and the proposed modules list, please see our 2.29 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.29.1 Development Release

2009-10-26T05:25:17Z

Hello all,

This announcement comes late but you knew it was coming. We are back
on a development track, new features are flowing, you should upload
tarballs now, as an extraordinary first step to an exciting future.

Tarballs are due on *today*, Monday October 26th, before 23:59 UTC
for the GNOME 2.29.1 Development Release, which will be delivered on
Wednesday. Modules which were proposed for inclusion should try to
follow the 2.29 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.1. 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!

For more informations about 2.29, the full schedule, the official
module lists and the proposed module lists, please see our colorful
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

Cheers,

Frederic
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.28.1 Release

2009-10-18T08:03:02Z

Heja,

Tarballs are due on 2009-10-19 before 23:59 UTC for the GNOME 2.28.1
release, which will be delivered on Wednesday.

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.28.1. 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!

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://live.gnome.org/TwoPointTwentynine

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

Thanks,

andre
--
mailto:ak-47@... | failed
http://www.iomc.de/ | http://blogs.gnome.org/aklapper

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Back on GNOME Bugzilla: weekly-bug-summary, describeuser

2009-10-06T08:17:37Z

Thanks to Frederic Peters, we have the following reports again:

1. https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.html
This URL has changed as it is now an extension.

2. https://bugzilla.gnome.org/page.cgi?id=describeuser.html
This URL has changed as it is now an extension. Every mailto: link on
show_bug.cgi (and so on) links to above report.

3. Patch report is now linked from browse.cgi.

These are extensions, but still use some GNOME Bugzilla specific
functionality. Plus sometimes relies on Bugzilla HEAD changes.
For the source: http://launchpad.net/bugzilla.gnome.org We solely use
Launchpad as Bugzilla upstream will use Bzr in future.

--
Regards,
Olav
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Celebrating the release of GNOME 2.28!

2009-09-23T15:54:06Z

======================================
Celebrating the release of GNOME 2.28!
======================================

Today, the GNOME Project celebrates the release of GNOME 2.28, the
latest version of the popular, multi-platform free desktop environment
and of its developer platform. Released on schedule, to the day, GNOME
2.28 builds on top of a long series of successful six months releases to
offer the best experience to users and developers.

For more than 10 years now, the project has been seeing a tremendous
amount of work. And as usual, it's hard to come back to a previous
version of GNOME once you've tried GNOME 2.28, which is probably the
best compliment the project can receive.

This six months effort wouldn't have been possible without the whole
GNOME community, made of contributors from all around the world:
hackers, documentors, usability and accessibility specialists,
translators, maintainers, sysadmins, companies, artists, users and
testers. GNOME would not exist without all those people. Thanks very
much to every one of them!

You'll find detailed information about GNOME 2.28 in our release notes:

http://library.gnome.org/misc/release-notes/2.28/

Most distributions have already started integrating GNOME 2.28 in their
development version, or as package updates to their stable version.

Some parties are already happening in various places to celebrate this
release. But tomorrow morning, you can be sure that GNOME contributors
will already be working on their plans for the next version of GNOME,
due in March, 2010.

Enjoy! And be proud of this release!

- The GNOME Release Team
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE (before Monday 23:59 UTC! don't forget translators!): GNOME 2.28.0 Final Release

2009-09-18T02:37:51Z

Hi all,

The 2.28.0 stable release is just a few days ahead! Time to celebrate! No,
no, not yet! First, let's make sure we roll the final/stable/perfect
tarballs for
all our modules! After that, then, yes, we can all celebrate the result of our
hard work in the last 6 months! Yay!

Tarballs are due on 2009-09-21 before 23:59 UTC for the GNOME 2.28.0
newstable 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.28.0. 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!

Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.

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

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

Thanks,

--lucasr
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.28.0 Release Candidate (2.27.92) Released!

2009-09-09T16:20:53Z

GNOME 2.28.0 Release Candidate (2.27.92)
========================================

We're a few days before the hard code freeze for 2.28.0, and having
tried 2.27.92, I think we have something good there. Actually, better
than just good. But well, we still have a few days to fix this pet bug
that annoys so many people -- I even heard that, in case you'd be a bit
late, some release team people can give +1 to freeze break requests if
you have the right arguments. And food is always a good argument. But I
can't tell who those people are. Or maybe I can, if you have the right
arguments...

To compile GNOME 2.27.92, you can use the jhbuild [3] modulesets [4]
(which use the exact tarball versions from the official release):

[3] http://library.gnome.org/devel/jhbuild/
[4] http://download.gnome.org/teams/releng/2.27.92/

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

platform - http://download.gnome.org/platform/2.27/2.27.92/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.92/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.92/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.92/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.92/NEWS

The GNOME 2.27.92 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.92/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.92/
admin sources - http://download.gnome.org/admin/2.27/2.27.92/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.92/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.92/

TESTING! TESTING! TESTING!
--------------------------

This release is a feature, user interface and string frozen snapshot
primarily intended for wide public scrutiny before the final GNOME 2.28
release in September. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.27, the full schedules and the official
modules list, please see our 2.27 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

bugzilla.gnome.org now redirects to SSL

2009-09-09T05:51:46Z

All accesses to bugzilla.gnome.org over normal HTTP are now redirected
to SSL (HTTPS). It has a valid, CA-signed certificate (by
StartCom--recognized by Firefox and Safari and will be recognized by IE
later this month).

If you'd like to see some of the reasoning behind enforcing SSL (as
opposed to just making it optional), see here:

https://bugzilla.gnome.org/show_bug.cgi?id=544234#c13

Anyhow, if you have scripts that interact with Bugzilla, they may not
be expecting this redirect, or may not work properly with SSL, so they
may have to be updated.

-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@...
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.28.0 Release Candidate (2.27.92)

2009-09-04T09:10:32Z

Cześć,

Yeah, right, GNOME 2.27.92 is due next week, bla bla bla, you know the
drill. Now that we're done with that, I'm requesting your opinion for
something really important. I mean, it will affect really a lot of
people. While visiting friends this week, I was able to say hi to some
of their new fishes in their aquarium. And it turns out they have a new
fish. They called it Times. Or Sabre. Depending who you ask. However,
for me it's Wanda because it really looks like Wanda. Not GNOME's
Wanda, but John Cleese's Wanda. But they don't think it's a good name
for the fish, so they reject what I think is the most appropriate name.
So what do you think? I'll be happy to hear from all of you!

And, hrm, please don't forget to work on critical bugs ;-) So if there
are some critical bugs that are annoying users, now is a good time to
fix them for 2.28.0!

Tarballs are due on Monday September 7th before 23:59 UTC for the GNOME
2.28.0 Release Candidate (2.27.92), which will be delivered on
Wednesday.

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.27.92. 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!

For more information about 2.27, the full schedule and the official
module lists, please see our colorful 2.27 page on the wiki:
http://live.gnome.org/TwoPointTwentyseven

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

Thanks,

Vincent

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.28.0 beta 2 (2.27.91) release!

2009-08-26T04:20:11Z

Hello all,

This is the seventh development release, and the second beta, towards
our 2.28 release that will happen in September 2009. By now most things
are in place, and your mission is easy: Go download it. Go compile it.
Go test it. And go hack on it, document it, translate it, fix it.

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

To compile GNOME 2.27.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.27.90/

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

platform - http://download.gnome.org/platform/2.27/2.27.91/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.91/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.91/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.91/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.91/NEWS
mobile - http://download.gnome.org/mobile/2.27/2.27.91/NEWS

The GNOME 2.27.91 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.91/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.91/
admin sources - http://download.gnome.org/admin/2.27/2.27.91/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.91/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.91/
mobile sources - http://download.gnome.org/mobile/2.27/2.27.91/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

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

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

Cheers,

The GNOME Release Team

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.27.91 beta tarballs due (and string freeze!)

2009-08-21T08:19:46Z

Hello all,

My laptop finally broke down but the new one is so fast I could
actually release GNOME 2.27.91 in five minutes; but then it would miss
the shiny new releases that you carefully planned for Monday, so I'll
refrain and follow the agreed schedule...

* TARBALLS *

Tarballs are due on 2009-08-24 before 23:59 UTC for the GNOME 2.27.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.27.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!

We are *serious* about this, we really want your tarballs, especially
if you skipped the last calls and have interesting things in Git; and
if don't have time, or your build environment is broken, or whatever,
please do tell us so we can prepare tarballs.

* STRING FREEZE *

The other important thing is that we are now entering string freeze:

No string changes may be made without confirmation from the i18n team
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.

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

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

Cheers,

Frederic
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.28.0 Beta 1 (2.27.90) Released!

2009-08-12T17:10:20Z

GNOME 2.28.0 Beta 1 (2.27.90) Released!
=======================================

This is the sixth development release, and the first beta, towards our
2.28 release that will happen in September 2009. By now most things are
in place, and your mission is easy: Go download it. Go compile it. Go
test it. And go hack on it, document it, translate it, fix it.

With this release, we are now even more frozen; developer API/ABI were
already, and at this point all new API are hopefully documented; no UI
changes may be made without approval from the release team and
notification to the documentation project, and no new features without
approval from the release team. We also remain in the string change
announcement period -- all string changes must be announced to both
the gnome-doc-list and gnome-i18n lists.

To compile GNOME 2.27.90, you can use GARNOME [1] (which supports users
and has additional/different modules available), or the jhbuild [2]
modulesets [3] (which use the exact tarball versions from the official
release):
[1] http://www.gnome.org/projects/garnome/
[2] http://library.gnome.org/devel/jhbuild/
[3] http://download.gnome.org/teams/releng/2.27.90/

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

platform - http://download.gnome.org/platform/2.27/2.27.90/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.90/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.90/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.90/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.90/NEWS
mobile - http://download.gnome.org/mobile/2.27/2.27.90/NEWS

The GNOME 2.27.90 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.90/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.90/
admin sources - http://download.gnome.org/admin/2.27/2.27.90/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.90/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.90/
mobile sources - http://download.gnome.org/mobile/2.27/2.27.90/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.27, the full schedules, the official
modules list and the proposed modules list, please see our 2.27 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Propose new modules for inclusion in GNOME 2.30/3.0

2009-08-10T07:45:21Z

Tonight at 23:59 UTC the period for proposing new modules for official
inclusion in GNOME starts.

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 end on Monday Oct 26th at 23:59
UTC. We expect discussion to heat up about those proposals around that
time and to reach a decision at the beginning of November.

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

For more information about 2.29, the full schedule, the official module
lists and the proposed module lists, please see our 2.27/2.29 page on
the wiki:
http://live.gnome.org/TwoPointTwentyseven

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

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Bugzilla Upgrade Scheduled For August 15-16

2009-08-08T21:40:22Z

Hello GNOME Developers and Bug Triagers! The code work for the Bugzilla
3.4 upgrade is complete, and after conferring with the infrastructure
team and the release team, we've set the date of the upgrade for
Saturday, August 15. I expect there to be roughly six hours of downtime
if everything goes well, starting at 9:00am Pacific time (that's 16:00
UTC). However, if anything goes wrong (and I don't expect it to--I've
already done several test upgrades), Bugzilla may possibly be down for
the entire weekend.

There is now a test server containing the data from bugzilla.gnome.org
as of about a week ago:

http://bugzilla-test.gnome.org/

Email is off on this installation, so you can play with it to your
heart's content. It does not affect the actual bugzilla.gnome.org when
you make changes on this server.

You should find the new server to be faster for every operation than
the old server. If you spot any performance problems, please report them
by sending me an email.

Please test this and report any bugs that you find! The best way to
report bugs at this point would just be to send me an email directly.
The user interface and feature set are pretty much fixed at this point,
so UI feedback cannot be acted upon until after the upgrade (unless it's
very minor tweaks). It would probably be best to stick to just bug
reports for now, in terms of feedback. If UI changes are desired or
required, bugs can be filed for them after the upgrade is complete.
(Preferably, if you want UI changes to Bugzilla, we'd like your help to
do them upstream, at bugzilla.org, not as local customizations to
bugzilla.gnome.org.)

It's particularly important to make sure that any Unicode data that you
have placed in Bugzilla is correctly displayed in this test instance,
because some of it (like comments) cannot be fixed very easily after the
final Bugzilla upgrade.

Please note that not all features from the old bugzilla.gnome.org have
been ported forward, only the features that were absolutely necessary to
perform the upgrade.

However, there are many new features, some of which are very
noticeable. For example, there's a "skins" system--check your Preferences.

The largest "new feature" that is specific to the GNOME Bugzilla is an
extension for Bugzilla called "traceparser". In the future this will be
publicly available for all Bugzillas, but at the moment it is specific
to the GNOME Bugzilla only. This does lots of very interesting things
with traces:

* It figures out the "interesting" thread(s) and displays only those
threads in comments (with a page you can click through to to see the
full trace).

* It displays stack traces "prettily", HTML-formatted, in comments.
(You can click through to see the raw trace.)

* It hides traces in comments by default, with a button to expand them.
If you want to always see traces, there is a preference for that in your
"Preferences" panel.

* It understands both Python and GDB stack traces.

* When a user files a bug in the web interface that contains a stack
trace, if there are similar or identical traces in the system, it offers
the user the opportunity to CC themselves on one of the bugs containing
the similar traces instead of continuing to file their bug. If their
trace is of higher quality than the trace currently on the bug, it will
also add their trace to the bug.

* Administrators and triagers can, for specific traces, say that
certain incoming traces should be *automatically* duped to specific
bugs, without the user being able to choose. If the bug is closed
(RESOLVED or VERIFIED), the user will simply receive a message saying
that they tried to file a duplicate of a closed bug, with a link to the
bug. If the bug is open, CCs them on the bug and attaches their trace if
it is of higher quality than the existing trace.

* There is a report that shows the most popular stack traces submitted.

If you have any questions about the upgrade in general, feel free to
respond on desktop-devel-list.

-Max
--
Max Kanat-Alexander
Chief Engineer
http://www.everythingsolved.com/
Everything Solved: Complete Computer Management

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.27.90 Development Release (and UI Freeze!)

2009-08-07T04:11:57Z

Hi all,

Today is a happy day, isn't it? Can you feel it!? Can you feel it!? Of course,
it's the day you all receive this nice call for tarballs! Awesome! Ok, I don't
feel very creative today. It's hard to beat Mr. Untz in the
Tarballs-Due-reminder
area... :-)

Tarballs are due on 2009-08-10 before 23:59 UTC for the GNOME 2.27.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.27.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.27, the full schedule, the official
module lists and the proposed module lists, please see our colourful 2.27
page:
http://www.gnome.org/start/unstable

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

Thanks,

--lucasr
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.27.5 released!

2009-07-29T15:15:32Z

GNOME 2.27.5 Development Release
================================

Wow, it's quite hot here. Sure, the temperature outside is high, but I
guess it's also because of this computer who worked hard to understand
some lines of code and to translate them into something that it can then
use to make me happy. Yes. Because running GNOME makes me happy! And
the 2.27.5 release is no exception there: it has this magic power on me.
It's a good release to get a first feeling of what will be in GNOME
2.28, with the new modules now being integrated and new features popping
here and there, in many differents modules. Ah, if only it could do
something for the temperature ;-)

Please note that this milestone marks the beginning of the feature
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/TwoPointTwentyseven/ReleaseNotes

You all know what you have to do now. Go download it. Go compile it. Go
test it. And go hack on it, document it, translate it, fix it.

To compile GNOME 2.27.5, 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.27.1/

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

platform - http://download.gnome.org/platform/2.27/2.27.5/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.5/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.5/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.5/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.5/NEWS

The GNOME 2.27.5 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.5/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.5/
admin sources - http://download.gnome.org/admin/2.27/2.27.5/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.5/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.5/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate
development status.

For more information about 2.27, the full schedules, the official
modules list and the proposed modules list, please see our 2.27 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Change: 2.30 Module proposal period starts August 10th

2009-07-29T14:46:40Z

In its last meeting the release-team decided to have an EARLIER module
proposal period for GNOME 2.30/3.0.

The new dates are:

NEW DATE (OLD DATE)
Aug 10 (Sep 07) Start of module proposal period for 2.30
Oct 26 same GNOME 2.29.1
Oct 26 (Nov 16) End of module proposal period for 2.30
Oct 26 (Dec 02) Discussions head up
Nov 2 (Dec 09) Release-Team decides
Nov 9 (Dec 14) Module freeze
Nov 18 same GNOME 2.29.2

Having an earlier period will probably be kept for the future.

http://live.gnome.org/TwoPointTwentyseven/ and the ical file for 2.28 at
http://www.gnome.org/start/unstable/schedule.ics have been updated
accordingly (the latter will be pushed in a few hours).

For general information on proposing modules for GNOME inclusion see
http://live.gnome.org/ReleasePlanning/ModuleProposing .

andre
--
mailto:ak-47@... | failed
http://www.iomc.de/ | http://blogs.gnome.org/aklapper

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.27.5 Development Release (and feature freeze!)

2009-07-24T12:06:31Z

Hi,

While a good number of our contributors was in Gran Canaria at the
beginning of the month, some people were at home working hard to
complete some features for GNOME 2.28. And we'll see the results of this
hard work in the next release! Oh, and I'm not implying the people who
attended the Desktop Summit/GUADEC didn't work hard -- they certainly
had a hard time with all the ice cream!

Also please note that this milestone marks the beginning of the feature
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/TwoPointTwentyseven/ReleaseNotes

Tarballs are due on Monday July 27th before 23:59 UTC for the GNOME
2.27.5 Development Release, which will be delivered on Wednesday.

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.27.5. 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!

For more informations about 2.27, the full schedule and the official
module lists, please see our colorful 2.27 page on the wiki:
http://live.gnome.org/TwoPointTwentyseven

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

Thanks,

Vincent

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

New module decisions for 2.28

2009-07-22T08:06:33Z

Hi,

The release team met on Sunday to see how sunburnt the various members
were. There were certainly big differences. Andre was bright red, while
some who shall stay anonymous were, hrm, untouched by the sun.
Afterwards, we managed to find a few minutes to discuss the new module
proposals.

Many thanks to the people who contributed to the discussion on the list,
and to the authors and maintainers of the proposed modules!

Short summary
=============

In:
gnome-bluetooth (desktop)
gnome-disk-utility (desktop)
libgdata (external dependency)
libseed (bindings)
DeviceKit-disks (external dependency)
WebKit/GTK+ (external dependency)
libchamplain (external dependency)

Out:
krb5-auth-dialog
icontool

General note about the hal migration: some modules (like
rhythmbox/banshee, even if not part of the GNOME modulesets) will rely
on udev in the future. This means they will need some work for
non-Linux-based OS. Help is needed to make sure this migration goes
smoothly for those platforms.

Details
=======

+ gnome-bluetooth (desktop)
- good doc, even an experimental port to mallard
- works great
=> approved
=> bluez becomes an approved external dependency
=> has a runtime dependency on obexd

+ gnome-disk-utility (desktop)
- stub documentation for the palimpset utility
- replaces gfloppy (in gnome-utils, already removed)
- needs a string review (techy ones, missing comments, etc.)
. Matthias can work with David on it next week
- Linux-only for now (but this is more related to DeviceKit-disks)
- optional dependency for gvfs right now
- provides libraries with no guarantee for API/ABI stability
=> approved
=> non-Linux-based OS won't be able to use it unless DeviceKit-disks
is ported there. We encourage people to work on those ports to
offer the best experience to GNOME users on those OS.

+ libgdata (desktop)
- good api doc
- required for the current version of totem youtube plugin, and maybe
later by evolution
- some worries about the protocol being only used by Google at the
moment (on non-free services)
- we certainly want to allow users to access their data, though
- technically not needed in the desktop
=> approved as external dependency

+ krb5-auth-dialog (desktop)
- reactive maintainer
- minimal doc
- suggestion to integrate it in seahorse or gnome-keyring
- no reply from the community
- neat tool, but that's not something that end users will directly
install themselves.
=> rejected because it doesn't really fit the desktop set
=> suggestion to integrate it in seahorse, though

+ libseed (bindings)
- was mainly rejected because of gjs vs seed for 2.26
- gnome-js-common was created to offer a common js module between gjs
and seed
- still, for reasons that are independent from the gjs and seed
teams, there are technical differences that makes it hard to write
code that can be used with both gjs and seed
- gnome-shell will likely stay with gjs, but seed people offered to
port it to seed
- we want people to start using js in GNOME now since it will likely
play an important role for the future
=> approved
=> people should write code that also works on gjs when possible,
since we might later decide that gjs is more appropriate

+ DeviceKit-disks (external dependency)
- clearly the right way forward
- DeviceKit-disks is not yet available on non-Linux systems
- it requires recent udev & kernel
- many things can already be done with gvfs only (no need for hal or
DeviceKit-disks)
=> approved
=> it's preferred to keep a hal backend when possible (instead of
just removing it) for portability reasons

+ WebKit/GTK+ (external dependency)
- good work done to fix issues
- still not perfect for accessibility
. we trust the WebKit/GTK+ team for fixing this
=> approved
=> the WebKit/GTK+ team needs to continue work on accessibility
=> modules with WebKit ports should merge the relevant branches (eg,
yelp)

+ libchamplain (external dependency)
- people like it
- needs to be ported to clutter 1.0
=> approved if ported to clutter 1.0

+ icontool (external dependency)
- no reply to the mail by Frederic (on June 10th)
- should replace icon-naming-utils
- mostly useful for one-canvas work (but from discussion with
artists, it's not completely ready yet)
- would the icontool-render be used during "make dist" or "make
install"?
=> rejected as it's not really needed now and we didn't get replies
to questions (it will probably be accepted when it's ready)

Thanks,

Vincent

--
Les gens heureux ne sont pas pressés.
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

Jhbuild moduleset: SHA256 hash instead of MD5

2009-07-20T08:35:34Z

As MD5 is insecure, the GNOME 2.28 modulesets in jhbuild have been
switched to SHA256 when using Python 2.5 or newer.

NOTE: Please still fill in the md5sum attribute for old Pythoners.

This has a few implications.

1. When adding new tarballs to a jhbuild moduleset file

Make sure to add it in the following format:

<branch module="releases/cairo-1.8.6.tar.gz" version="1.8.6"
repo="cairo.org"
hash="sha256:93a347af0cecf258be8fb54265b16a0fb16317df4a32896141d2987c30773535"
md5sum="4e64139ef6f668df24450f3b81dd0771" size="6616544">

The hash attribute is new and its value MUST be prefixed with "sha256:".
Jhbuild does support other hash methods (whatever Python allows), but
please only use sha256.

IMPORTANT: Make sure to still fill in the md5sum attribute. This for
people with Python 2.4 or before (our RHEL5 buildbot).

2. For people with Python 2.4 or lower

Jhbuild will only look at the hash attribute in case the md5sum wasn't
specified. This to try and ensure you'll still be able to verify the
tarballs with md5.

3. People with custom modulesets

Jhbuild will still look at the md5sum attribute in case the hash
attribute is not specified (with some special exception for Python 2.4
or lower).
Meaning: everything will work as before (file a bug if not)

4. People with an old jhbuild

After committing the sha256 modulesets I noticed a small bug how jhbuild
handled the hash attribute. In any case, please do a 'git pull --rebase'
in case you receive errors.

5. People using the release team modulesets

The tarball modulesets provided by the release team as of 2.27.5 will
only contain a SHA256 hash. When using these modulesets on Python 2.4 or
before you will get a warning about an unsupported hash method.

The release team moduleset are files such as:
http://download.gnome.org/teams/releng/2.27.4/gnome-suites-2.27.4.modules

--
Regards,
Olav
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

API/ABI Freeze for GNOME 2.27

2009-07-19T16:15:50Z

Hi,

API/ABI Freeze for GNOME 2.27 starts today (Monday) by 23:59 UTC.

No API or ABI changes should be made in the platform libraries (for
instance, no new functions, no changed function signatures or struct
fields).
API freeze is not required for non-platform libraries, but is
recommended.

Future freezes (and other deadlines):

+ Feature and Module Freeze, July 27th
+ New API must be documented, August 3rd
+ Writing of release notes begins, August 3rd
+ UI Freeze, starting August 10th
+ String Freeze, starting August 24th
+ Hard Code Freeze, starting September 14th

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

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

Thanks,
andre
--
mailto:ak-47@... | failed
http://www.iomc.de/ | http://blogs.gnome.org/aklapper

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.27.4 released!

2009-07-15T09:38:21Z

Hello all,

This is already the 4th development release towards our 2.28 release
that will happen in October 2009; this release comes just after the
first joint GNOME / KDE conference, which was certainly great fun for
all present people.

To compile GNOME 2.27.4, 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.27.4/

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

platform - http://download.gnome.org/platform/2.27/2.27.4/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.4/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.4/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.4/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.4/NEWS

The GNOME 2.27.4 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.4/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.4/
admin sources - http://download.gnome.org/admin/2.27/2.27.4/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.4/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.4/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is buildable
and usable, it is primarily intended for testing and hacking purposes.
GNOME uses odd minor version numbers to indicate development status.

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

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

Cheers,

Frederic
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.27.4 unstable tarballs due (and more)

2009-07-12T04:35:29Z

Hello all!

You are now all back from GCDS, and the release team would like to
inform you about the following:

* GNOME 2.27.4 unstable tarballs due
* String Change Announcement Period
* UI Change Announcement Period
* Module inclusion discussion heats up

Tarballs are due on 2009-07-13 before 23:59 UTC for the GNOME 2.27.4
unstable 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.27.4. 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!

String Change Announcement Period

After the GNOME 2.27.4 release, string changes must be announced to
gnome-doc-list and gnome-i18n.

UI Change Announcement Period

After the GNOME 2.27.4 release, UI changes must be announced to
gnome-doc-list.

Module inclusion discussion heats up

Soon we'll have a r-t meeting regarding the module proposals.

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

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

Thanks,
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.26.3 released!

2009-07-01T16:19:00Z

==================================================================
GNOME 2.26.3 Stable Release
==================================================================

This is the last update to GNOME 2.26. It contains many fixes for
important bugs that directly affect our users, documentation updates
and also a large number of updated translations. Many thanks to all
the contributors who worked hard on delivering those changes in time.
We hope it will help people feel better in their daily use of computers!

Meanwhile, the GNOME community is actively working on the unstable
branch of GNOME that will become GNOME 2.28 in September 2009.

The GNOME 2.26 release notes are available at:

http://library.gnome.org/misc/release-notes/2.26/

The notes that describe the changes between 2.26.2 and 2.26.3 are here:

admin - http://download.gnome.org/admin/2.26/2.26.3/NEWS
bindings - http://download.gnome.org//bindings/2.26/2.26.3/NEWS
desktop - http://download.gnome.org/desktop/2.26/2.26.3/NEWS
devtools - http://download.gnome.org/devtools/2.26/2.26.3/NEWS
mobile - http://download.gnome.org/mobile/2.26/2.26.3/NEWS
platform - http://download.gnome.org/platform/2.26/2.26.3/NEWS

The GNOME 2.26.3 release is available here:

admin sources - http://download.gnome.org/admin/2.26/2.26.3/
bindings sources - http://download.gnome.org/bindings/2.26/2.26.3/
desktop sources - http://download.gnome.org/desktop/2.26/2.26.3/
devtools sources - http://download.gnome.org/devtools/2.26/2.26.3/
mobile sources - http://download.gnome.org/mobile/2.26/2.26.3/
platform sources - http://download.gnome.org/platform/2.26/2.26.3/

To compile GNOME 2.26.3, 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.26.3/

We hope you'll love it,

The GNOME Release Team
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.26.3 stable tarballs due

2009-06-29T00:38:20Z

Hello all,

Whoohoooh!! Nice and sunny weather, time to thank that you have
air-conditioning and create some tarballs[1] for us. We'd prefer if
these tarballs are released from your 2.26 stable branch, this as there
only a few hours left until the 2.26.3 'tarballs due' deadline.
Some of the release team members (ok, me) can't make it to GUADEC, so
please 'meet, plan, party' for me :-)

and the usual nitty gritty 'blah blah blah' stuff:
Tarballs are due on 2009-06-29 before 23:59 UTC for the GNOME 2.26.3
stable 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.26.3. 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!

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

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

Thanks,
Them iceloving GNOME release team

[1] The plural is intentional. If you're only responsible for one
module, be aware that you can easily takeover one of the unmaintained
modules. In case you found some new dude(tte) to takeover one of
your modules, just start something new and exciting.

PS: In case the weather in your location isn't nice: think of GUADEC
PS2: In case you do not have air-conditioning: I know the feeling

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

GNOME 2.27.3 Released!

2009-06-18T04:52:36Z

GNOME 2.27.3 Development Release
================================

This is the third development release towards the wonderful 2.28
release!
Various bug fixes and nice improvements in several modules. Fun, fun,
fun!

To compile GNOME 2.27.3, 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.27.3/

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

platform - http://download.gnome.org/platform/2.27/2.27.3/NEWS
desktop - http://download.gnome.org/desktop/2.27/2.27.3/NEWS
admin - http://download.gnome.org/admin/2.27/2.27.3/NEWS
bindings - http://download.gnome.org/bindings/2.27/2.27.3/NEWS
devtools - http://download.gnome.org/devtools/2.27/2.27.3/NEWS
mobile - http://download.gnome.org/mobile/2.27/2.27.3/NEWS

The GNOME 2.27.3 release is available here:

platform sources - http://download.gnome.org/platform/2.27/2.27.3/
desktop sources - http://download.gnome.org/desktop/2.27/2.27.3/
admin sources - http://download.gnome.org/admin/2.27/2.27.3/
bindings sources - http://download.gnome.org/bindings/2.27/2.27.3/
devtools sources - http://download.gnome.org/devtools/2.27/2.27.3/
mobile sources - http://download.gnome.org/mobile/2.27/2.27.3/

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is buildable
and usable, it is primarily intended for testing and hacking purposes.
GNOME uses odd minor version numbers to indicate development status.

For more information about 2.27, the full schedules, the official
modules list and the proposed modules list, please see our 2.27 page:
http://www.gnome.org/start/unstable/

Also take a look at the abbreviated schedule reminder page at:
http://live.gnome.org/Schedule

We hope you'll love it,

The GNOME Release Team

--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list

TARBALLS DUE: GNOME 2.27.3 Development Release

2009-06-12T09:09:24Z

Hello, fellow hackers,

You thought you could have a nice week-end, enjoying sun and ice
creams... Guess what ? You were wrong ! Yes, my friends, you will have
to code the entire week-end, for what reason ? Release tarballs for
GNOME 2.27.3 Development release. Too bad ;-) (Of course, if you are
lazy or want to enjoy a non hacking week-end, you can still upload
your tarballs right now...).

Tarballs are due on Monday June 15th (this Monday) before 23:59 UTC
for the GNOME 2.27.3 Development Release, which will be delivered on
Wednesday. Modules which were proposed for inclusion should try to
follow the 2.27 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.27.3. 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!

For more information about 2.27, the full schedule, the official
module lists and the proposed module lists, please see our colorful
2.27 page on the wiki:
http://live.gnome.org/TwoPointTwentyseven

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

Thanks,
--
Frederic Crozat
Mandriva
--
devel-announce-list mailing list
devel-announce-list@...
http://mail.gnome.org/mailman/listinfo/devel-announce-list