public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Working Group established to evaluate the stable tree
Date: Tue, 16 Aug 2016 11:19:21 +1200	[thread overview]
Message-ID: <20160816111921.0b91bc89@katipo2.lan> (raw)
In-Reply-To: <CAGfcS_nEwX9epsGYYTBPpkVw-d2M4mq4bxB+x7kJU5tACjZEXA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4126 bytes --]

On Mon, 15 Aug 2016 09:37:33 -0400
Rich Freeman <rich0@gentoo.org> wrote:

> 
> Today developers tend to use views that exclude resolved bugs.
> Perhaps tomorrow they'll tend to use views that exclude bugs that are
> resolved or waiting for stabilization.  Perhaps these views will
> become the defaults.

Can bugzilla have a selection of templated parameterized searches? 

I Know you can have predefined searches and predefined shared searches, but
I didn't notice any parameterizable ones.

Subsequently, I've been getting around this using 

https://metacpan.org/release/BZ-Client

And some perl scripts that help me out.

Pre-defined query types I have are:

"Stabilizing mode: Find packages I mention that have changed in <X> time"

"Keywording mode: Find packages I mention that have either STABLEREQ or KEYWORDREQ keywords in all time"

Those names I use are not very descriptive, because "Keywording mode" is more used for research into
why keywords are what they are than it is for actual keywording, and its for helping determine which packages
are "Redundant and can be pruned".

Importantly, these searches also search /comment text/, because stablereqs and keyword reqs for specific
packages can't be identified by their SUBJECT on a regular basis.

 KEYWORDING=1 perl ~/bin/bzquery.pl ExtUtils::MakeMaker
Searching for "(?i)ExtUtils(::|-)MakeMaker"
3 entries in summary
~ 6yr  3mo   317877 -   FIXED RESOLVE : Please keyword perl-core/ExtUtils-MakeMaker (and perl-core/ExtUtils-Command perl-core/ExtUtils-Manifest perl-core/ExtUtils-Install) (updated: ~ 6yr  3mo )
~ 6yr  3dy   330387 -   FIXED RESOLVE : Please stabilize virtual/perl-ExtUtils-MakeMaker and deps (updated: ~ 5yr 11mo )
~ 4yr  6mo   400469 - WONTFIX RESOLVE : Please stabilize =perl-core/ExtUtils-MakeMaker-6.590.0 (updated: ~ 4yr  5mo )
10 entries in description
~ 9yr  2mo   180246 -   FIXED RESOLVE : Please stabilize =dev-perl/PDF-Create-1.04 (was: dev-perl/PDF-Create-0.06.1b corrupted console output during compile) (updated: ~ 6yr  8mo )
~ 6yr  2mo   321235 -   FIXED RESOLVE : Please stabilize dev-perl/GnuPG-Interface-0.42 (updated: ~ 5yr 11mo )
~ 6yr  2dy   329525 -   FIXED RESOLVE : Please stabilize =dev-perl/FileHandle-Unget-0.16.23 (updated: ~ 5yr 10mo )
~ 5yr  5mo   357599 - WONTFIX RESOLVE : Please (re-)keyword perl-core/Module-Build, perl-core/CPAN-Meta, perl-core/Version-Requirements, perl-core/Module-Metadata, perl-core/Perl-OSType (updated: ~ 2yr  3mo )
~ 4yr  7mo   395297 -   FIXED RESOLVE : Please stabilize =dev-perl/Moose-2.40.200 (updated: ~ 4yr  4mo )
~ 4yr  4mo   410367 -   FIXED RESOLVE : Please stabilize =dev-perl/XML-Parser-2.410.0 (updated: ~ 4yr  2mo )
~ 4yr  2mo   418803 -   FIXED RESOLVE : Please stabilize =dev-perl/DateTime-TimeZone-1.460.0 and deps (updated: ~ 3yr 11mo )
~ 3yr  6mo   456568 -   FIXED RESOLVE : Please stabilize =dev-perl/DateTime-TimeZone-1.560.0 (updated: ~ 3yr  3mo )
~ 2yr  4mo   504786 -   FIXED RESOLVE : =dev-lang/perl-5.18.2-r1 and related virtuals stabilization (updated: ~ 1yr  9mo )
~ 8mo  5dy   567482 -         CONFIRM : dev-lang/perl-5.22.2 perl-core/* virtual/perl-* stabilization (updated: ~ 2Hr 38Ms )


 STABILIZING=1 perl ~/bin/bzquery.pl ExtUtils::MakeMaker
Searching for "(?i)ExtUtils(::|-)MakeMaker"
0 entries in summary
4 entries in description
~ 3yr 10mo   435304 - WORKSFO RESOLVE : app-portage/g-cpan-0.16.* generates broken ebuild depending on perl-g-cpan instead of dev-perl modules (updated: ~ 4dy  9Hr )
~ 8mo  5dy   567482 -         CONFIRM : dev-lang/perl-5.22.2 perl-core/* virtual/perl-* stabilization (updated: ~ 2Hr 41Ms )
~ 2mo  4dy   585048 -         CONFIRM : sys-apps/texinfo-6.1 has weird build system, likely causing unneeded perl-cleaner rebuilds (updated: ~ 1dy 12Hr )
~ 1mo  2dy   586718 - WORKSFO RESOLVE : app-misc/screen-4.4.0 - makeinfo ./screen.texinfo -o screen.info : Can't locate Locale/Messages.pm in @INC (you may need to install the Locale::Messages module) (updated: ~ 1mo  4dy )

^^^ Doing anything like this on bugzilla directly is self abuse at present.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-15 23:20 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 21:35 [gentoo-dev] New Working Group established to evaluate the stable tree Kristian Fiskerstrand
2016-08-14 21:45 ` Ciaran McCreesh
2016-08-14 21:49   ` Kristian Fiskerstrand
2016-08-14 21:49   ` Kent Fredric
2016-08-14 21:52     ` M. J. Everitt
2016-08-14 22:06     ` Chris Reffett
2016-08-14 21:50   ` Anthony G. Basile
2016-08-14 21:57     ` Ciaran McCreesh
2016-08-14 22:01       ` Kent Fredric
2016-08-15 19:18       ` Andreas K. Hüttel
2016-08-15 19:19         ` Michael Orlitzky
2016-08-15  3:45 ` Jason Zaman
2016-08-15  3:53   ` Kent Fredric
2016-08-15  4:05     ` Jason Zaman
2016-08-15  7:55       ` Brian Dolbec
2016-08-15  8:50         ` Kent Fredric
2016-08-15 10:21         ` Kristian Fiskerstrand
2016-08-18  6:33           ` Daniel Campbell
2016-08-15 13:40         ` Rich Freeman
2016-08-15 15:48           ` Brian Dolbec
2016-08-15  4:29 ` #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree) Kent Fredric
2016-08-15  4:37   ` Kent Fredric
2016-08-15 12:22     ` james
2016-08-15 12:49   ` Dirkjan Ochtman
2016-08-15 13:03     ` Kristian Fiskerstrand
2016-08-15 13:15       ` Dirkjan Ochtman
2016-08-15 13:25         ` Kristian Fiskerstrand
2016-08-15 14:28           ` james
2016-08-15 18:24           ` Dirkjan Ochtman
2016-08-15 19:30       ` Andreas K. Hüttel
2016-08-15 19:42         ` Rich Freeman
2016-08-21  0:30           ` Daniel Campbell
2016-10-04 17:25             ` Ian Stakenvicius
2016-10-07  2:40               ` Daniel Campbell
2016-08-15 23:00         ` Kent Fredric
2016-08-15 22:50       ` Kent Fredric
2016-08-15  8:00 ` [gentoo-dev] New Working Group established to evaluate the stable tree Pacho Ramos
2016-08-15  8:15   ` Pacho Ramos
2016-08-15 14:19   ` William Hubbs
2016-08-15 14:49     ` Kristian Fiskerstrand
2016-08-15 14:50       ` Kristian Fiskerstrand
2016-08-15 16:12         ` William Hubbs
2016-08-15 17:31           ` William Hubbs
2016-08-15 18:33             ` Rich Freeman
2016-08-15 19:12               ` William Hubbs
2016-08-15 19:27                 ` Rich Freeman
2016-08-15 20:01                   ` William Hubbs
2016-08-15 20:05                     ` Rich Freeman
2016-08-16  8:02                     ` [gentoo-dev] " Duncan
2016-08-16 13:52                       ` William Hubbs
2016-08-17  8:52                     ` [gentoo-dev] " Pacho Ramos
2016-08-17  8:50                   ` Pacho Ramos
2016-08-17 13:07                     ` Rich Freeman
2016-08-17 14:25                       ` Pacho Ramos
2016-08-18  7:32                     ` Raymond Jennings
2016-08-15 11:36 ` Kristian Fiskerstrand
2016-08-15 12:24 ` Michael Orlitzky
2016-08-15 13:37   ` Rich Freeman
2016-08-15 23:19     ` Kent Fredric [this message]
2016-08-15 19:33 ` Markus Meier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160816111921.0b91bc89@katipo2.lan \
    --to=kentnl@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox