Re: [arch-general] [arch-dev-public] Assigning bugs proposal
Tobias Powalowski wrote:
Hi guys. quite a lot of bug assigning happened lately, could you please add: [packagename] ... at the beginning of each bug topic, this way it's much easier to sort things on bugtracker.
thanks greetings tpowa
Hi Yes I can do it. ;) I did the change in some task but not in others. Another thing is that I think is important in changing the "status" field if task is assigned, it's much simpler to manage and allocate the missing. Many task are currently assigned to people but this field is in "unconfirmed". There any objection if I change the "status" to all the task currently assigned, but this field does not reflect the state? Unconfirmed -> Assigned (if task have people assigned) Good Luck! -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
On Sun, May 31, 2009 at 14:11, Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
There any objection if I change the "status" to all the task currently assigned, but this field does not reflect the state? Unconfirmed -> Assigned (if task have people assigned) +1 from me
Daenyth Blank wrote:
On Sun, May 31, 2009 at 14:11, Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
There any objection if I change the "status" to all the task currently assigned, but this field does not reflect the state? Unconfirmed -> Assigned (if task have people assigned)
+1 from me
Done for all! (both unconfirmed and currently assigned) Now all task in bugtracker under "Arch Linux" are assigned :) The only "unconfirmed" are these that wait for closure: FS#13018 FS#13069 FS#13661 FS#13948 FS#14290 FS#14436 FS#14680 Good Luck! -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
Gerardo Exequiel Pozzi wrote:
Tobias Powalowski wrote:
Hi guys. quite a lot of bug assigning happened lately, could you please add: [packagename] ... at the beginning of each bug topic, this way it's much easier to sort things on bugtracker.
thanks greetings tpowa
Hi
Yes I can do it. ;)
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :) There are plans in mind for a next Bug Squashing Day? PS: Sorry for many mails that implies the renames. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :)
There are plans in mind for a next Bug Squashing Day?
PS: Sorry for many mails that implies the renames
The last one was the end of March so that makes it ~2.5 months since the old one. It is best not to have these too frequently as motivation drops. I think it would be fine if we organise one for about 1 months time. Allan
On Sun, Jun 7, 2009 at 4:54 AM, Allan McRae<allan@archlinux.org> wrote:
Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :)
There are plans in mind for a next Bug Squashing Day?
PS: Sorry for many mails that implies the renames
The last one was the end of March so that makes it ~2.5 months since the old one. It is best not to have these too frequently as motivation drops. I think it would be fine if we organise one for about 1 months time.
Allan
+1 Although now that Gerardo is a bug wrangler, the bug tracker is in much better shape than before. The most crucial thing IMO is getting the bugs assigned quickly. Well done Gerardo. :) -- Greg
+1 and kudos to Gerardo! Sebastien On Sun, Jun 7, 2009 at 2:49 PM, Grigorios Bouzakis<grbzks@gmail.com> wrote:
On Sun, Jun 7, 2009 at 4:54 AM, Allan McRae<allan@archlinux.org> wrote:
Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :)
There are plans in mind for a next Bug Squashing Day?
PS: Sorry for many mails that implies the renames
The last one was the end of March so that makes it ~2.5 months since the old one. It is best not to have these too frequently as motivation drops. I think it would be fine if we organise one for about 1 months time.
Allan
+1
Although now that Gerardo is a bug wrangler, the bug tracker is in much better shape than before. The most crucial thing IMO is getting the bugs assigned quickly. Well done Gerardo. :)
-- Greg
Sébastien Duquette wrote:
+1 and kudos to Gerardo!
Sebastien
On Sun, Jun 7, 2009 at 2:49 PM, Grigorios Bouzakis<grbzks@gmail.com> wrote:
On Sun, Jun 7, 2009 at 4:54 AM, Allan McRae<allan@archlinux.org> wrote:
Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :)
There are plans in mind for a next Bug Squashing Day?
PS: Sorry for many mails that implies the renames
The last one was the end of March so that makes it ~2.5 months since the old one. It is best not to have these too frequently as motivation drops. I think it would be fine if we organise one for about 1 months time.
Allan
OK, I understand the reason. So the wiki page maybe needs to be update [#1] "Bug Squshing Day takes place during _*the first Sunday of every month*._".
+1
Although now that Gerardo is a bug wrangler, the bug tracker is in much better shape than before. The most crucial thing IMO is getting the bugs assigned quickly. Well done Gerardo. :)
-- Greg
Thanks. I believe that maintaining good order and updated the bugtracker is very important. It makes the community more friendly. :P [#1] http://wiki.archlinux.org/index.php/Bug_Squashing_Day -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
Gerardo Exequiel Pozzi wrote:
OK, I understand the reason. So the wiki page maybe needs to be update [#1] "Bug Squshing Day takes place during _*the first Sunday of every month*._".
Well, It could take place that often if there was motivation, but it appeared to die out so I guess there is not much... Feel free to change the wiki. Allan
On Sat, Jun 06, 2009 at 05:24:16PM -0300, Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :) Thanks for the hard work.
PS: Sorry for many mails that implies the renames. Don't worry. Bumping lost/forgotten tasks helps a lot to reduce the number of open bugs :)
On Mon, Jun 8, 2009 at 6:28 AM, Alessandro Doro<ordo.ad@gmail.com> wrote:
On Sat, Jun 06, 2009 at 05:24:16PM -0300, Gerardo Exequiel Pozzi wrote:
And done all posible renames of tasks to the form "[pkgname] the title". Bugtracker now looks much more orderly. and the function "Bug Reports" from package view page, works better :) In the last week more than 100 old task was closed :) Thanks for the hard work.
PS: Sorry for many mails that implies the renames. Don't worry. Bumping lost/forgotten tasks helps a lot to reduce the number of open bugs :)
Did the guideline for naming bugs with the [package] prefix end up in the relevant places? I know flyspray has a place for instructions, and I believe we have a wiki article as well. -Dan
On Mon, Jun 8, 2009 at 15:12, Dan McGee<dpmcgee@gmail.com> wrote:
Did the guideline for naming bugs with the [package] prefix end up in the relevant places? I know flyspray has a place for instructions, and I believe we have a wiki article as well.
It was in the header of every page in Arch Linux project on bugtracker for long time, but I think not more than 20% of users named reports that way, and I didn't think about changing all report titles to that standard (thanks for the work on renaming all open reports this way, Gerardo!), but after a wiki page was created - there's no mention of [pkgname] prefix anywhere. I've added a short guideline: http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines#Summary Please feel free to improve it, I'm a bad writer. -- Roman Kyrylych (Роман Кирилич)
participants (8)
-
Alessandro Doro
-
Allan McRae
-
Daenyth Blank
-
Dan McGee
-
Gerardo Exequiel Pozzi
-
Grigorios Bouzakis
-
Roman Kyrylych
-
Sébastien Duquette