On Sun, 13 Sep 2009 12:24:23 -0400
Tristan Van Berkom tristan.van.ber...@gmail.com wrote:
Guys,
Im sorry I missed the memo if there was one, I woke up this
morning to a full page of bugmail, deleting valid bugs from the
buglist and throwing them into a NEEDINFO state.
Javier pointed me
Am Donnerstag, den 17.09.2009, 15:26 -0400 schrieb Tristan Van Berkom:
So the bottom line is basically this: if you feel this should
be the minimum standard of attention that a maintainer must
absolutely pay to his buglist, then so be it, but I think you are
being unfair to ask this of me.
On Fri, Sep 18, 2009 at 04:15:19PM +0200, Pietro Battiston wrote:
Then, once someone offers to be the glade bugs maintainer, I think we
could ask that he checks every bug once a year.
You're restating what has been suggested.
If a bug is valid, mark it as NEW. It was already proposed that the
Am Freitag, den 18.09.2009, 16:15 +0200 schrieb Pietro Battiston:
Il giorno ven, 18/09/2009 alle 13.44 +0200, Andre Klapper ha scritto:
Yes, I expect maintainers should be able to take a look at the incoming
bug reports at least once in 12 months.
Then, once someone offers to be the glade
Hi all,
Sorry first for the delay in responding. We've been discussing the concerns
raised on the list, and we've tried our best to address them in a synthetic
way. Here are a couple of thoughts and remarks that respond to Colin, Sandy
and other people's comments and clarify a few things.
If you tried to activate mDNS bookmarks in vinagre, you'd get:
(vinagre:5842): GLib-GObject-CRITICAL **: g_value_get_object: assertion
`G_VALUE_HOLDS_OBJECT (value)' failed
** (vinagre:5842): CRITICAL **: vinagre_bookmarks_entry_get_node: assertion
`VINAGRE_IS_BOOKMARKS_ENTRY (entry)' failed
Hey,
2009/9/18 Bastien Nocera had...@hadess.net:
If you tried to activate mDNS bookmarks in vinagre, you'd get:
(vinagre:5842): GLib-GObject-CRITICAL **: g_value_get_object: assertion
`G_VALUE_HOLDS_OBJECT (value)' failed
** (vinagre:5842): CRITICAL **: vinagre_bookmarks_entry_get_node:
Am Freitag, den 18.09.2009, 18:45 +0100 schrieb Lucas Rocha:
2009/9/18 Bastien Nocera had...@hadess.net:
https://bugzilla.gnome.org/show_bug.cgi?id=581817
Approval 1/2.
--lucasr
Approval 2/2.
andre
--
mailto:ak...@gmx.net | failed
http://www.iomc.de/ | http://blogs.gnome.org/aklapper
On Fri, Sep 18, 2009 at 7:44 AM, Andre Klapper ak...@gmx.net wrote:
Am Donnerstag, den 17.09.2009, 15:26 -0400 schrieb Tristan Van Berkom:
So the bottom line is basically this: if you feel this should
be the minimum standard of attention that a maintainer must
absolutely pay to his buglist,
Epiphany is branched for 2.28, the branch name is gnome-2-28.
Cheers,
Xan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
On Thu, 2009-09-17 at 10:32 -0500, C de-Avillez wrote:
On Sun, 13 Sep 2009 12:24:23 -0400
Tristan Van Berkom tristan.van.ber...@gmail.com wrote:
Guys,
Im sorry I missed the memo if there was one, I woke up this
morning to a full page of bugmail, deleting valid bugs from the
buglist
Tristan,
I believe you could just ask the bugsquad to kindly skip over glade3
bugs if their policy doesn't work for you or causes you more work.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
Hi Tristan,
Am Freitag, den 18.09.2009, 14:16 -0400 schrieb Tristan Van Berkom:
On Fri, Sep 18, 2009 at 7:44 AM, Andre Klapper ak...@gmx.net wrote:
Am Donnerstag, den 17.09.2009, 15:26 -0400 schrieb Tristan Van Berkom:
So the bottom line is basically this: if you feel this should
be the
On Fri, Sep 18, 2009 at 7:20 PM, Andre Klapper ak...@gmx.net wrote:
and avoiding having a database with lots of
outdated ancient bugs).
Can you elaborate a bit on what the higher level goals of closing the
bugs is? They still remain in the database, no? Is the issue speed
of queries on the
On Fri, Sep 18, 2009 at 3:20 PM, Andre Klapper ak...@gmx.net wrote:
[...]
So to summarize, the question boils down to:
Are you able to take a look at the latest glade3 bug reports once a
year? If not, glade3 probably has to be excluded from the policy.
I receive bugmail for all bugs and I am
Hi,
has there been any progress on porting gnome-shell to using seed instead
of gjs? It sounds kind of silly to use two JavaScript engines, and to
reintroduce a dependency on Gecko after having finally managed to get
rid of it.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend
2009/9/18 Josselin Mouette j...@debian.org:
Hi,
has there been any progress on porting gnome-shell to using seed instead
of gjs? It sounds kind of silly to use two JavaScript engines, and to
reintroduce a dependency on Gecko after having finally managed to get
rid of it.
I'm not aware of
So we have these fancy branch notification emails that
get automatically sent to gnome-doc-list, gnome-i18n,
and release-team whenever somebody creates a stable
branch.
Given that, do we need to continue sending out branch
notifications by hand? It basically means that we get
two notifications
On Fri, Sep 18, 2009 at 12:20 PM, Andre Klapper ak...@gmx.net wrote:
We are sorry on *not* having communicated with the rest of GNOME about
this change, but we believed that all developers subscribed to bugs.
We would very much like to know which other mailing lists we should add
on.
The only
Hey,
This is to let you know that gnome-disk-utility has branched for 2.28,
the branch name is gnome-2-28. New development happens on master.
Thanks,
David
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
On Fri, 2009-09-18 at 14:28 -0400, Owen Taylor wrote:
I think for most modules, confirming bugs has usually seemed like a
waste of of the maintainer's time. Confirming bugs assumes that the
maintainer isn't looking at bugs until they are confirmed. Once the
maintainer is already looking at a
21 matches
Mail list logo
