You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jochen Kemnade <ke...@gmail.com> on 2014/05/12 19:51:40 UTC
Issues with bulk-close-candidate label
Hi,
on 2013-01-14, in an effort to close some outdated JIRA issues, Uli
added the label bulk-close-candidate to every issue that "has been last
updated more than 1.5 years ago, has no assignee, affects an old version
of Tapestry that is not actively developed anymore, and is therefore
prone to be bulk-closed in the near future".
Also, he asked the reporter to update the issue if it still was ...
well, an issue.
There are 31 issues that haven't been updated since:
https://bit.ly/1ld7yXJ
or jql:
project = TAP5 AND labels = bulk-close-candidate AND status = Open and
updatedDate < "2013-01-14 15:47"
I'd say we just close those with another friendly comment. What do you
think?
I guess, we should also repeat this procedure for issues that affect
only versions before 5.3.
Jochen
Re: Issues with bulk-close-candidate label
Posted by Robert Zeigler <ro...@roxanemy.com>.
+1
GATAATGCTATTTCTTTAATTTTCGAA
> On May 12, 2014, at 3:22 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> Well, obviously, we haven't managed the issue list very well, and it got a
> bit out of control.
>
> I'm in favor of closing them; they've had over a year to sit and gather
> attention.
>
> We have more than enough bugs to keep us busy! I've been trying to close a
> few myself.
>
>
>> On Mon, May 12, 2014 at 10:51 AM, Jochen Kemnade <ke...@gmail.com> wrote:
>>
>> Hi,
>>
>> on 2013-01-14, in an effort to close some outdated JIRA issues, Uli
>> added the label bulk-close-candidate to every issue that "has been last
>> updated more than 1.5 years ago, has no assignee, affects an old version
>> of Tapestry that is not actively developed anymore, and is therefore
>> prone to be bulk-closed in the near future".
>> Also, he asked the reporter to update the issue if it still was ...
>> well, an issue.
>> There are 31 issues that haven't been updated since:
>>
>> https://bit.ly/1ld7yXJ
>> or jql:
>> project = TAP5 AND labels = bulk-close-candidate AND status = Open and
>> updatedDate < "2013-01-14 15:47"
>>
>> I'd say we just close those with another friendly comment. What do you
>> think?
>> I guess, we should also repeat this procedure for issues that affect
>> only versions before 5.3.
>>
>> Jochen
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
> @hlship
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Howard Lewis Ship <hl...@gmail.com>.
Well, obviously, we haven't managed the issue list very well, and it got a
bit out of control.
I'm in favor of closing them; they've had over a year to sit and gather
attention.
We have more than enough bugs to keep us busy! I've been trying to close a
few myself.
On Mon, May 12, 2014 at 10:51 AM, Jochen Kemnade <ke...@gmail.com> wrote:
> Hi,
>
> on 2013-01-14, in an effort to close some outdated JIRA issues, Uli
> added the label bulk-close-candidate to every issue that "has been last
> updated more than 1.5 years ago, has no assignee, affects an old version
> of Tapestry that is not actively developed anymore, and is therefore
> prone to be bulk-closed in the near future".
> Also, he asked the reporter to update the issue if it still was ...
> well, an issue.
> There are 31 issues that haven't been updated since:
>
> https://bit.ly/1ld7yXJ
> or jql:
> project = TAP5 AND labels = bulk-close-candidate AND status = Open and
> updatedDate < "2013-01-14 15:47"
>
> I'd say we just close those with another friendly comment. What do you
> think?
> I guess, we should also repeat this procedure for issues that affect
> only versions before 5.3.
>
> Jochen
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Issues with bulk-close-candidate label
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 09 Jan 2015 21:34:18 -0200, Ulrich Stärk <ul...@spielviel.de> wrote:
> +1
+11
>
> On 2015-01-09 23:00, Howard Lewis Ship wrote:
>> I'm all for that!
>>
>> On Fri, Jan 9, 2015 at 10:43 AM, Jochen Kemnade <ke...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> also, there are 26 issues whose "affects version" field is empty. In
>>> May
>>> 2014, I added a comment to each of them, asking if they were relevant
>>> in
>>> 5.3.7 or 5.4-beta-6 but they are still in the same state.
>>>
>>>
>>> https://issues.apache.org/jira/browse/TAP5-1872?jql=project%20%3D%20TAP5%20AND%20status%20%3D%20Open%20and%20affectedVersion%20is%20EMPTY%20and%20updated%20%3E%20%222014-05-30%22%20and%20updated%20%3C%20%222014-05-31%22
>>>
>>> If nobody objects by Monday, I'll close them as invalid too.
>>>
>>> Jochen
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Ulrich Stärk <ul...@spielviel.de>.
+1
On 2015-01-09 23:00, Howard Lewis Ship wrote:
> I'm all for that!
>
> On Fri, Jan 9, 2015 at 10:43 AM, Jochen Kemnade <ke...@gmail.com> wrote:
>
>> Hi,
>>
>> also, there are 26 issues whose "affects version" field is empty. In May
>> 2014, I added a comment to each of them, asking if they were relevant in
>> 5.3.7 or 5.4-beta-6 but they are still in the same state.
>>
>>
>> https://issues.apache.org/jira/browse/TAP5-1872?jql=project%20%3D%20TAP5%20AND%20status%20%3D%20Open%20and%20affectedVersion%20is%20EMPTY%20and%20updated%20%3E%20%222014-05-30%22%20and%20updated%20%3C%20%222014-05-31%22
>>
>> If nobody objects by Monday, I'll close them as invalid too.
>>
>> Jochen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'm all for that!
On Fri, Jan 9, 2015 at 10:43 AM, Jochen Kemnade <ke...@gmail.com> wrote:
> Hi,
>
> also, there are 26 issues whose "affects version" field is empty. In May
> 2014, I added a comment to each of them, asking if they were relevant in
> 5.3.7 or 5.4-beta-6 but they are still in the same state.
>
>
> https://issues.apache.org/jira/browse/TAP5-1872?jql=project%20%3D%20TAP5%20AND%20status%20%3D%20Open%20and%20affectedVersion%20is%20EMPTY%20and%20updated%20%3E%20%222014-05-30%22%20and%20updated%20%3C%20%222014-05-31%22
>
> If nobody objects by Monday, I'll close them as invalid too.
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Issues with bulk-close-candidate label
Posted by Jochen Kemnade <ke...@gmail.com>.
Hi,
also, there are 26 issues whose "affects version" field is empty. In May
2014, I added a comment to each of them, asking if they were relevant in
5.3.7 or 5.4-beta-6 but they are still in the same state.
https://issues.apache.org/jira/browse/TAP5-1872?jql=project%20%3D%20TAP5%20AND%20status%20%3D%20Open%20and%20affectedVersion%20is%20EMPTY%20and%20updated%20%3E%20%222014-05-30%22%20and%20updated%20%3C%20%222014-05-31%22
If nobody objects by Monday, I'll close them as invalid too.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Jochen Kemnade <ke...@gmail.com>.
Hi,
There are 56 JIRA issues that have the "bulk-close-candidate" label.
That means that they affect versions before 5.3, a comment has been
added more than half a year ago to update them if they are relevant in
5.4-beta-22 and they weren't.
https://issues.apache.org/jira/browse/TAP5-13?jql=project%20%3D%20TAP5%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20bulk-close-candidate
If nobody objects by Monday, I'll close them as invalid.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Jochen Kemnade <ke...@gmail.com>.
I'll do it once beta 6 is publicly available, then people can check their
issues against that.
Re: Issues with bulk-close-candidate label
Posted by Ulrich Stärk <ul...@spielviel.de>.
+1
On 2014-05-15 15:22, Jochen Kemnade wrote:
> Am 13.05.2014 17:29, schrieb Jochen Kemnade:
>> Alright, I just closed the issues that have not been modified since
>> Uli's comment. I also removed the bulk-close-candidate from the ones
>> that had newer changes.
>> Now, do we want to repeat the process with
>>
>> project = TAP5 AND status = Open AND assignee in (EMPTY) and
>> affectedVersion not in (5.4, 5.3, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.4,
>> 5.3.5, 5.3.6, 5.3.7) and updatedDate < "2013-01-01"
>>
>> ?
>
> If no-one objects within three days, I'll assume lazy consensus and add the bulk-close-candidate
> label to those issues (currently 97) with an appropriate comment, asking the reporters to check if
> they are still valid and either close or update them.
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Jochen Kemnade <jo...@eddyson.de>.
Am 13.05.2014 17:29, schrieb Jochen Kemnade:
> Alright, I just closed the issues that have not been modified since
> Uli's comment. I also removed the bulk-close-candidate from the ones
> that had newer changes.
> Now, do we want to repeat the process with
>
> project = TAP5 AND status = Open AND assignee in (EMPTY) and
> affectedVersion not in (5.4, 5.3, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.4,
> 5.3.5, 5.3.6, 5.3.7) and updatedDate < "2013-01-01"
>
> ?
If no-one objects within three days, I'll assume lazy consensus and add
the bulk-close-candidate label to those issues (currently 97) with an
appropriate comment, asking the reporters to check if they are still
valid and either close or update them.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Jochen Kemnade <jo...@eddyson.de>.
Alright, I just closed the issues that have not been modified since
Uli's comment. I also removed the bulk-close-candidate from the ones
that had newer changes.
Now, do we want to repeat the process with
project = TAP5 AND status = Open AND assignee in (EMPTY) and
affectedVersion not in (5.4, 5.3, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.4,
5.3.5, 5.3.6, 5.3.7) and updatedDate < "2013-01-01"
?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Issues with bulk-close-candidate label
Posted by Ulrich Stärk <ul...@spielviel.de>.
+1
On 2014-05-12 19:51, Jochen Kemnade wrote:
> Hi,
>
> on 2013-01-14, in an effort to close some outdated JIRA issues, Uli added the label
> bulk-close-candidate to every issue that "has been last updated more than 1.5 years ago, has no
> assignee, affects an old version of Tapestry that is not actively developed anymore, and is
> therefore prone to be bulk-closed in the near future". Also, he asked the reporter to update
> the issue if it still was ... well, an issue. There are 31 issues that haven't been updated
> since:
>
> https://bit.ly/1ld7yXJ or jql: project = TAP5 AND labels = bulk-close-candidate AND status =
> Open and updatedDate < "2013-01-14 15:47"
>
> I'd say we just close those with another friendly comment. What do you think? I guess, we
> should also repeat this procedure for issues that affect only versions before 5.3.
>
> Jochen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org