Mamoru Tasaka | 14 May 15:11
Picon

Merge reviews marked as triage target

Hello.

About one hour ago many merge reviews are marked as triage targets like:
https://www.redhat.com/archives/fedora-package-review/2008-May/msg01109.html

In my recognition this must not happen because all packages in Fedora must pass
merge reviews (or review requests) and these merge requests should not be closed
automatically. Generally speaking all bugs with component "package review" should
not be closed by triagers, should be?

Regards,
Mamoru

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

John Poelstra | 28 Mar 19:44
Picon
Favicon

NOTICE: fedora-triage-list is being re-purposed

Greetings,

This is a short public service announcement to let you know that the bug 
triage process has been recently relaunched and we'd love to have you 
join us.

All the current details are here:
http://fedoraproject.org/wiki/BugZappers

A couple months ago the BugZappers decided to conduct all of their 
business on fedora-test-list <at> redhat.com because of the already 
established audience there and the absence of traffic on fedora-triage-list.

As a result, we are clearing this mailing list of all its members now.

In the short-term we will be using this mailing list to collect email 
notifications for the Fedora bugzilla cleanup to be launched very soon 
which is described here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

Essentially the user making all of the mass changes will be 
fedora-triage-list <at> redhat.com

Anyone is welcome to resubscribe to fedora-triage-list if you are 
interested in viewing these notifications.

John

--

-- 
fedora-test-list mailing list
(Continue reading)

Jon Stanley | 1 Jan 17:25
Picon

Bringing this back to life

Hey -

I was zapping really old FC6 kernel bugs, and got a most interesting
response to one.  There is definitely the perception that we're not
doing our "jobs".  Fedora is not $DAYJOB for me, but it is something
that I take a keen interest in., and so do as much as I possibly can
on my own time.  Therefore, it's kind of disheartening to see comments
like the one below.  I'll also include the response that I gave to the
reporter.

In discussing this on fedora-marketing-list, it's apparent that there
aren't enough folks doing triage - this list hasn't been touched since
April, for instance.  Like I said Fedora is not $DAYJOB for me, so I
can't really spend much time during the days.  However, in the
evenings and on weekends (I'm US/Eastern), I'll work as hard as need
be.  Let's get some bug evenings/weekends together, and we can make
some good stuff happen hopefully.

------- Additional Comments From grgoffe@...  2007-12-31
18:48 EST -------
Jon,

Thanks for your input.

I've pretty much given up with my efforts to further the Fedora cause. Here are
my reasons:

1) I opened this case OVER a year ago. NO responses til now. Not exactly what I
would call a timely response I'm sure you'll agree.

(Continue reading)

riley.marquis | 21 Dec 04:05

Bugzilla Ideas For 2008

Greetings!
I had a few ideas which I hope will be helpful to the Fedora Bug Squad, so
I thought I would run them by everybody and get a discussion going to see
exactly how helpful these ideas might be.

1: Dedicated Fedora Bugzilla
Should we copy all the Fedora bugs, incl. bugs for the Fedora Directory
Server, to a new host, e.g. bugs.fedoraproject.org or
bugzilla.fedoraprojhect.org?  I was thinking this might be one way to
minimize strain on our Bugzilla servers.  I know this could be a very time
consuming project, so we should only do this if it is worth the hassle.

2: Add An "Expired" Tag To Bugzilla
Should both the Redhat and Fedora Bugzillas have a new tag added to the
system, called "Expired" (or whatever name we wish) for all tickets which
have had x amount of days with no activity, instead of simply calling it
"Closed"?  I was thinking this might allow the bug squad to more easily
find unresolved issues, esp. long-awaited features such as encrypted
filesystems.

3: Old Bug Deletion/Archival
Should we delete bugs that have been closed for x amount of time, esp. the
ones that we will likely never again need to reference, such as fc6 and
earlier bugs?  If deletion is not an option, perhaps we should setup a
legacy server to store these old bugs, as it will be hardly used and make
more resources available for new Fedora bugs?  If we can use it, perhaps
bugs.fedoralegacy.org or bugzilla.fedoralegacy.org?

4: Contingency Plan
I know Bugzilla is a very important part of our infrastructure, and
(Continue reading)

Magyar Zoltán | 27 Apr 02:21
Picon

starting to contribute

Hi!

My name is Zoltan. I'm from Hungary, and I would like to start to contribute to the fedora project.
I thought about bug triaging, but I want to ask for an example: let's see this bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237409
First I tried and was able to reproduce it (with the given components and versions). I didn't find duplicates for that bug, and I think that the provided info is sufficient to be helpful.
So should I only add myself to the CC list, and leave a comment, that it should be assigned (and maybe the priority set to low)?
Thanks in advance!
Zoli

--
fedora-triage-list mailing list
fedora-triage-list@...
https://www.redhat.com/mailman/listinfo/fedora-triage-list
A S Alam | 26 Apr 14:35
Picon
Favicon

any meeting for QA/Triage Team?

Hi Team
just want to know is there any meeting for QA / Bugzapper team?

thanks
--

-- 
A S Alam
#fedora-l10n (freenode)
tz GMT+5:30
"Either find a way or Make one"

--
fedora-triage-list mailing list
fedora-triage-list@...
https://www.redhat.com/mailman/listinfo/fedora-triage-list

Lex Hider | 10 Apr 00:39
Favicon

209857 can be closed?

Just starting a little bit of triage.
I think the below bug can now be closed.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209857

Cheers,
Lex.

--
fedora-triage-list mailing list
fedora-triage-list@...
https://www.redhat.com/mailman/listinfo/fedora-triage-list


Gmane