Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 May 2017 08:29:09 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 217515] [exp-run] Update PostgreSQL default version to 9.5
Message-ID:  <bug-217515-13-fy45Frn75u@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217515-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-217515-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217515

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open

--- Comment #27 from Kubilay Kocak <koobs@FreeBSD.org> ---
tl;dr Close this issue when the "QA/exp-run/approval by portmgr" 'task' is
satisfied. To be less confusing, the attachment here should be deleted so
there's no confusion as to which patch needs to be exp-run and which one is=
 the
'latest'.

The current state is that this issue is a sub(task) issue of bug 201796, and
that QA (this issue) blocks the change/commit (the other issue) and given t=
he
relationship is set that way.

>From a workflow perspective, given it has been setup this way already, this
issue should be closed once QA is satisfied/confirmed, which essentially
becomes the "approved by: portmgr" for the other bug.

All else being equal, the cleanest, least confusing way is a single bug with
all the conversation, all the qa, process and all the approval in one place,
*UNLESS* there are multiple steps/tasks to achieve a single 'goal' and each
task sits with a different assignee/maintainer.

Example where multiple issues with one parent "goal" task is: one security
vulnerability affecting mysql/maridb/percona/whatever, each with a different
maintainer and a vuxml entry and quarterly merge done by someone else (say
ports-secteam). The parent is assigned to ports-secteam (as
coordinator/responsible), with subtasks per port affected, and the subtasks=
 are
assigned to and actioned by the respective maintainers.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217515-13-fy45Frn75u>