Re: What is the procedure for reporting bugs against 'broken' git commits?

Here is the comment (extracted from a bug I filed) that told me I should not file bugs against development versions:

2009-05-17 09:29 UTC [reply]
Please do not abuse the bug-tracker for getting help with problems building the
development version from git. We have a mailing-list for such questions.

And please use stable versions of GLib and GTK+.
Note that this was a bug in a development release of an application


________________________________
From: Simos Xenitellis <simos.lists@xxxxxxxxxxxxxx>
To: BugByteMan <bugbyteman@xxxxxxxxx>
Cc: gnome-list@xxxxxxxxx
Sent: Saturday, June 27, 2009 2:01:44 PM
Subject: Re: What is the procedure for reporting bugs against 'broken' git commits?

On Sat, Jun 27, 2009 at 9:51 PM, BugByteMan<bugbyteman@xxxxxxxxx> wrote:
Hi,

I have not been able to find the procedure for reporting bugs against
'broken' git commits.  I was told that 'bugzilla' is not to be used for this
purpose.

The following glib commit breaks native building on windows/mingw:

http://git.gnome.org/cgit/glib/commit/?id=7662c86611bf44175f18ec6eb66f159040ac73c5

The change to gio/glocalfileinfo.c
removed an #ifdef S_ISLNK which breaks windows (symbolic links
not supported)

I would like to prevent this from making it into an official glib release
but I have not found the appropriate way to report bugs on pre-release code.

This list is a user list (not developer).
For glib-related matters, ask at gtk-devel-list,
http://mail.gnome.org/archives/gtk-devel-list/2009-March/msg00097.html

I do not know why would someone tell you not to report such issue to Bugzilla.
If you have a reference to that conversation (if it's public), it
would help to figure out the rational.
My view is that you either mention this to the gtk-devel-list or file
it under bugzilla, mentioning that it's a regression.

Simos



_______________________________________________
gnome-list mailing list
gnome-list@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gnome-list

Relevant Pages

  • Re: F13 Sadly Unusable
    ... Reporting bugs? ... The kernel guys are over-swamped with open bugs (I've got at least 4 of ... the developers triage and fix this bug. ...
    (Fedora)
  • Re: What is the procedure for reporting bugs against broken git commits?
    ... development version from git. ... , and report any bugs on those. ... the GNOME Bugzilla. ... What is the procedure for reporting bugs against 'broken' git ...
    (GNOME)
  • Re: Searching for small Bug Tracking System
    ... of Mozilla-Forum to post bugs, ... Reporting bugs per web is the ... Sure when using myisam tables mysql is not acid compliant However, you can choose to use innodb and then it is. ... What other security problems do exist for mysql? ...
    (Debian-User)
  • Re: Tell Sun what applications you want
    ... I believe reporting bugs is reserved only for customers with a ... > and asking questions, which go directly to the development engineers. ... It's the bugs and questions which go directly to the development engineers, ...
    (comp.unix.solaris)
  • Re: The Phantom Update
    ... bugzilla _before_ they file bugs please. ... development time every day just replying to bugs and linking ...
    (Fedora)