From dev-return-36673-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Thu Nov 29 09:44:32 2012 Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 656F9D33F for ; Thu, 29 Nov 2012 09:44:32 +0000 (UTC) Received: (qmail 12101 invoked by uid 500); 29 Nov 2012 09:44:32 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 11961 invoked by uid 500); 29 Nov 2012 09:44:31 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 11934 invoked by uid 99); 29 Nov 2012 09:44:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 09:44:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jan.haderka@magnolia-cms.com designates 109.71.96.11 as permitted sender) Received: from [109.71.96.11] (HELO mail.magnolia-cms.com) (109.71.96.11) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 09:44:22 +0000 X-Spam-Level: *** X-Footer: bWFnbm9saWEtY21zLmNvbQ== Received: from [10.99.122.144] ([90.183.155.218]) (authenticated user jan.haderka@magnolia-cms.com) by mail.magnolia-cms.com (Kerio Connect 7.4.3) (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for dev@jackrabbit.apache.org; Thu, 29 Nov 2012 10:44:00 +0100 From: Jan Haderka Content-Type: multipart/alternative; boundary="Apple-Mail=_CFE2AE30-2ACC-45F4-A8C3-158A8E7B74BA" Message-Id: <7282C511-F42F-4713-9D8B-D33DC331B514@magnolia-cms.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: issues fixed by nobody? Date: Thu, 29 Nov 2012 10:44:01 +0100 References: <3095D151-8433-46B4-A3B7-E8A602FC99C0@magnolia-cms.com> To: dev@jackrabbit.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, hits=3.9 required=7.0 tests=AWL: -0.122,BAYES_99: 4.07,HTML_MESSAGE: 0.001, TOTAL_SCORE: 3.949,autolearn=no --Apple-Mail=_CFE2AE30-2ACC-45F4-A8C3-158A8E7B74BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On Nov 29, 2012, at 9:57 AM, Stefan Guggisberg = wrote: > On Thu, Nov 29, 2012 at 9:44 AM, Jan Haderka > wrote: >> Hiya, >>=20 >> there appears to be fair number of issues in JR that were fixed by = "unassigned". Is this on purpose? >>=20 >> = https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/= temp/SearchRequest.html?jqlQuery=3Dproject+%3D+JCR+AND+status+%3D+closed+a= nd+assignee+is+null&tempMax=3D1000 >=20 > FWIW: they were not 'assigned' to a particular user, that doesn't mean > they were fixed by 'unassigned'. > the user who resolved the issue can be found in the issue's history. Yeah, I know. I should have perhaps phrased the question better, sorry = about that.=20 For what purpose do you use the assignee? Is it just to nominate the = person to fix the issue or the person who should manage the process or = something else? What does it mean if the issue is unassigned by the time = when it was closed? It is that it was spontaneous fix made by developer = and was unmanaged/unplanned or that no one in particular feels = responsibility for it or something else? Thx. --Apple-Mail=_CFE2AE30-2ACC-45F4-A8C3-158A8E7B74BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
On Nov 29, 2012, = at 9:57 AM, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:

On Thu, Nov 29, 2012 at 9:44 AM, Jan Haderka
<
jan.haderka@magnolia-cms.com<= /a>> wrote:
Hiya,

there appears = to be fair number of issues in JR that were fixed by "unassigned". Is = this on purpose?

https://issues.apache.org/= jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jq= lQuery=3Dproject+%3D+JCR+AND+status+%3D+closed+and+assignee+is+null&te= mpMax=3D1000

FWIW: they were not 'assigned' to a = particular user, that doesn't mean
they were fixed by = 'unassigned'.
the user who resolved the issue can be found in the = issue's history.

Yeah, I know. I should = have perhaps phrased the question better, sorry about = that. 

For what purpose do you use the = assignee? Is it just to nominate the person to fix the issue or the = person who should manage the process or something else? What does it = mean if the issue is unassigned by the time when it was closed? It is = that it was spontaneous fix made by developer and was = unmanaged/unplanned or that no one in particular feels responsibility = for it or something = else?

Thx.


= --Apple-Mail=_CFE2AE30-2ACC-45F4-A8C3-158A8E7B74BA--