You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christine Poerschke (BLOOMBERG/ LONDON)" <cp...@bloomberg.net> on 2017/04/07 16:32:56 UTC
Resolved --> Closed transition for 6.4 release issues
Hi Everyone,
Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA issues works?
I just noticed that some 6.4 tickets are still marked 'Resolved' rather than 'Closed' which surprised me. This JQL finds them: "status = Resolved and project in (LUCENE,SOLR) and fixVersion=6.4"
Thanks,
Christine
Re: Resolved --> Closed transition for 6.4 release issues
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
I was marking cases Resolved when I push the actually final changes in
and then Closed several days later if nothing broke/no feedback came
back.
But I am probably doing it wrong and it has to be manually tracked.
Regards,
Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced
On 7 April 2017 at 17:36, David Smiley <da...@gmail.com> wrote:
> I suppose it's debatable wether public knowledge of a version being released
> or not is itself sufficient to serve this purpose. I certainly am keenly
> aware of the latest version as I think we all are here? Personally I'd
> prefer the simplicity of one less state but I don't care that much either.
>
> On Fri, Apr 7, 2017 at 1:08 PM Chris Hostetter <ho...@fucit.org>
> wrote:
>>
>>
>> : For me I use "closed" to figure out if an issue was just committed or if
>> : there is already a release out there. So to me it is natural to close
>>
>> And to continue that line of thinking: the reason this should be important
>> is so that we don't inadvertantly "tack on" any work/tweaks to issues that
>> have already been released.
>>
>> If SOLR-XXXX is a bug fix that was committed to the 6.Y.Z, but after 6.Y.Z
>> is released people discuss/debate the merits of tweaking the fix, the fact
>> that 6.Y.Z is already out -- and SOLR-XXXX is "Closed" -- is the reminder
>> that this change should be tracked in a new, distinct, jira ... if for no
>> other reason so that the "new work" has it's own Jira to be listed under
>> in CHANGES, but also so that if/when we talk about a bug that was
>> "fixed by SOLR-XXXX" people looking at that jira can all be on the same
>> page about what that means, and what releases include that fix.
>>
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
> --
> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
> http://www.solrenterprisesearchserver.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Resolved --> Closed transition for 6.4 release issues
Posted by David Smiley <da...@gmail.com>.
I suppose it's debatable wether public knowledge of a version being
released or not is itself sufficient to serve this purpose. I certainly am
keenly aware of the latest version as I think we all are here? Personally
I'd prefer the simplicity of one less state but I don't care that much
either.
On Fri, Apr 7, 2017 at 1:08 PM Chris Hostetter <ho...@fucit.org>
wrote:
>
> : For me I use "closed" to figure out if an issue was just committed or if
> : there is already a release out there. So to me it is natural to close
>
> And to continue that line of thinking: the reason this should be important
> is so that we don't inadvertantly "tack on" any work/tweaks to issues that
> have already been released.
>
> If SOLR-XXXX is a bug fix that was committed to the 6.Y.Z, but after 6.Y.Z
> is released people discuss/debate the merits of tweaking the fix, the fact
> that 6.Y.Z is already out -- and SOLR-XXXX is "Closed" -- is the reminder
> that this change should be tracked in a new, distinct, jira ... if for no
> other reason so that the "new work" has it's own Jira to be listed under
> in CHANGES, but also so that if/when we talk about a bug that was
> "fixed by SOLR-XXXX" people looking at that jira can all be on the same
> page about what that means, and what releases include that fix.
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
> --
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com
RE: Resolved --> Closed transition for 6.4 release issues
Posted by Chris Hostetter <ho...@fucit.org>.
: For me I use "closed" to figure out if an issue was just committed or if
: there is already a release out there. So to me it is natural to close
And to continue that line of thinking: the reason this should be important
is so that we don't inadvertantly "tack on" any work/tweaks to issues that
have already been released.
If SOLR-XXXX is a bug fix that was committed to the 6.Y.Z, but after 6.Y.Z
is released people discuss/debate the merits of tweaking the fix, the fact
that 6.Y.Z is already out -- and SOLR-XXXX is "Closed" -- is the reminder
that this change should be tracked in a new, distinct, jira ... if for no
other reason so that the "new work" has it's own Jira to be listed under
in CHANGES, but also so that if/when we talk about a bug that was
"fixed by SOLR-XXXX" people looking at that jira can all be on the same
page about what that means, and what releases include that fix.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: Resolved --> Closed transition for 6.4 release issues
Posted by Uwe Schindler <uw...@thetaphi.de>.
FYI,
to do the transition:
- apply the filter as you did already
- choose top right "Tools" -> "Bulk change all issues"
- select status transition to closed, click on the selct all button above the list
- don't foget to uncheck "send e-mail" on last page of the process
- wait a few seconds until JIRA did the transition.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@thetaphi.de]
> Sent: Friday, April 7, 2017 6:52 PM
> To: dev@lucene.apache.org
> Subject: RE: Resolved --> Closed transition for 6.4 release issues
>
> Hi,
>
> For me I use "closed" to figure out if an issue was just committed or if there is
> already a release out there. So to me it is natural to close all issues after the
> release. It's just a bulk change, takes like 2 minuten per project (most of the
> time is setting the filter and then clicking through the bulk change API).
>
> Uwe
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> > -----Original Message-----
> > From: Erick Erickson [mailto:erickerickson@gmail.com]
> > Sent: Friday, April 7, 2017 6:40 PM
> > To: dev@lucene.apache.org; Christine Poerschke
> > <cp...@bloomberg.net>
> > Subject: Re: Resolved --> Closed transition for 6.4 release issues
> >
> > My question is "Why do we even have two?".
> >
> > If we don't have any real use for having both, I'd vote for removing one.
> >
> > I see Steve's comment but would still ask whether having two serves
> > enough good purpose to be worth the confusion. Does anyone really
> > _use_ this distinction? Or is it just another thing to get wrong when
> > resolving a ticket as well as be another task for the RM?
> >
> > Don't particularly have any strong feelings here, but thought it worth
> asking.
> >
> > Erick
> >
> > On Fri, Apr 7, 2017 at 9:32 AM, Christine Poerschke (BLOOMBERG/
> > LONDON) <cp...@bloomberg.net> wrote:
> > > Hi Everyone,
> > >
> > > Does anyone recall how the 'Resolved' to 'Closed' status transition for
> JIRA
> > issues works?
> > >
> > > I just noticed that some 6.4 tickets are still marked 'Resolved' rather than
> > 'Closed' which surprised me. This JQL finds them: "status = Resolved and
> > project in (LUCENE,SOLR) and fixVersion=6.4"
> > >
> > > Thanks,
> > > Christine
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: Resolved --> Closed transition for 6.4 release issues
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
For me I use "closed" to figure out if an issue was just committed or if there is already a release out there. So to me it is natural to close all issues after the release. It's just a bulk change, takes like 2 minuten per project (most of the time is setting the filter and then clicking through the bulk change API).
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Erick Erickson [mailto:erickerickson@gmail.com]
> Sent: Friday, April 7, 2017 6:40 PM
> To: dev@lucene.apache.org; Christine Poerschke
> <cp...@bloomberg.net>
> Subject: Re: Resolved --> Closed transition for 6.4 release issues
>
> My question is "Why do we even have two?".
>
> If we don't have any real use for having both, I'd vote for removing one.
>
> I see Steve's comment but would still ask whether having two serves
> enough good purpose to be worth the confusion. Does anyone really
> _use_ this distinction? Or is it just another thing to get wrong when
> resolving a ticket as well as be another task for the RM?
>
> Don't particularly have any strong feelings here, but thought it worth asking.
>
> Erick
>
> On Fri, Apr 7, 2017 at 9:32 AM, Christine Poerschke (BLOOMBERG/
> LONDON) <cp...@bloomberg.net> wrote:
> > Hi Everyone,
> >
> > Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA
> issues works?
> >
> > I just noticed that some 6.4 tickets are still marked 'Resolved' rather than
> 'Closed' which surprised me. This JQL finds them: "status = Resolved and
> project in (LUCENE,SOLR) and fixVersion=6.4"
> >
> > Thanks,
> > Christine
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Resolved --> Closed transition for 6.4 release issues
Posted by Erick Erickson <er...@gmail.com>.
My question is "Why do we even have two?".
If we don't have any real use for having both, I'd vote for removing one.
I see Steve's comment but would still ask whether having two serves
enough good purpose to be worth the confusion. Does anyone really
_use_ this distinction? Or is it just another thing to get wrong when
resolving a ticket as well as be another task for the RM?
Don't particularly have any strong feelings here, but thought it worth asking.
Erick
On Fri, Apr 7, 2017 at 9:32 AM, Christine Poerschke (BLOOMBERG/
LONDON) <cp...@bloomberg.net> wrote:
> Hi Everyone,
>
> Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA issues works?
>
> I just noticed that some 6.4 tickets are still marked 'Resolved' rather than 'Closed' which surprised me. This JQL finds them: "status = Resolved and project in (LUCENE,SOLR) and fixVersion=6.4"
>
> Thanks,
> Christine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Resolved --> Closed transition for 6.4 release issues
Posted by Steve Rowe <sa...@gmail.com>.
The Resolved->Closed transition is supposed to be done by release managers - see item #2 at <https://wiki.apache.org/lucene-java/ReleaseTodo#Update_JIRA>.
--
Steve
www.lucidworks.com
> On Apr 7, 2017, at 12:32 PM, Christine Poerschke (BLOOMBERG/ LONDON) <cp...@bloomberg.net> wrote:
>
> Hi Everyone,
>
> Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA issues works?
>
> I just noticed that some 6.4 tickets are still marked 'Resolved' rather than 'Closed' which surprised me. This JQL finds them: "status = Resolved and project in (LUCENE,SOLR) and fixVersion=6.4"
>
> Thanks,
> Christine
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org