Bug 228918 - Do we need to add a PR thing for regression / tagging PRs?
Summary: Do we need to add a PR thing for regression / tagging PRs?
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: Rodney W. Grimes
Depends on:
Blocks: 228911
  Show dependency treegraph
Reported: 2018-06-12 08:43 UTC by Rodney W. Grimes
Modified: 2018-09-08 06:46 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Rodney W. Grimes freebsd_committer 2018-06-12 08:43:38 UTC
Do we need to add a PR thing for regression / tagging PRs?
Comment 1 Rodney W. Grimes freebsd_committer 2018-06-12 08:44:43 UTC
Unassigned at dev summit, holding as @rgrimes until I can find someone to take lead on this item.
Comment 2 Ed Maste freebsd_committer 2018-06-12 11:20:19 UTC
We can see how using meta PR 228911 works for this purpose?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2018-06-12 21:22:00 UTC
I agree that with these recent PRs from the devsummit preparing for 12, we should come up with some way to quickly find them.  I we can agree on some kind of Keyword, I'll do the work.

fwiw we already have a Keyword 'regression' which may be searched as follows:


178 bugs found.

There are probably 146 relevant to the src tree, of which the plurality are "recent" for some definition of recent.  I am willing to help triage these.
Comment 4 Rodney W. Grimes freebsd_committer 2018-06-12 21:39:28 UTC
(In reply to Mark Linimon from comment #3)
You can very quickly find them, they are ALL in the blocks: PR 228911
so if you follow up to that from any of them you can see the full tree
below that.

One of them, the OpenSSL 1.1 one now has all the ports that are causing OpenSSL 1.1 issues, etc.

There are some others that have come into that tree.

Please do not just go adding PRs to the tree without some talk, as RE@ well soon be getting spammed with all this email.

I thought about keywords and tags, but the root PR is probably the best solution at this time.
Comment 5 Ed Maste freebsd_committer 2018-06-19 00:59:43 UTC
(In reply to Mark Linimon from comment #3)
And the full set of bugs are available as a convenient tree: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=228911&hide_resolved=1
Comment 6 Ed Maste freebsd_committer 2018-07-31 16:07:07 UTC
Should we close this PR now?
Comment 7 Rodney W. Grimes freebsd_committer 2018-07-31 16:12:04 UTC
(In reply to Ed Maste from comment #6)
We could, but I would actually like to see something more formalized added to documentation someplace about this Meta bug usage for releases and also for possibly tracking the "have, need, want" process that occurs at each Dev Summit.

From my perspective the later, the have need want process, is a black hole process.  We do it, those present know about it, pictures get taken, and then it trips over the event horizon into the void.

Solicity Thoughts and input
Comment 8 Ed Maste freebsd_committer 2018-07-31 21:10:46 UTC
(In reply to Rodney W. Grimes from comment #7)
Good point, presumably the use of tracking PRs should be included in releng process documentation.

I'm not sure what the best place for have/need/want or devsummit next release planning would be, but agreed we should do that as well.
Comment 9 Mark Linimon freebsd_committer freebsd_triage 2018-09-05 14:45:21 UTC
koobs and I agreed that adding a "tracking" keyword would be useful.  I have done so.
Comment 10 Rodney W. Grimes freebsd_committer 2018-09-05 14:55:04 UTC
(In reply to Mark Linimon from comment #9)
Though I agree the process of making this decision should of at least included RE@.
Comment 11 Mark Linimon freebsd_committer freebsd_triage 2018-09-08 06:46:26 UTC
Apparently I misunderstood my discussion with koobs@.  There is as of yet no conensus.

If people want to remove the new keyword from this or another of the other PRs I added, I will have no objection.

I will be stepping away from this topic at this time.