This morning I finished reviewing the last of these issues. Only four
remain untouched, all of which were previously autoclosed and
reopened, so we shouldn't autoclose them again.
I didn't keep track of exact numbers of how many I closed,
reprioritized, duped, marked abandoned etc. There were a
sorry for typo, in the backlog they should not be closed because they are
serious bugs and need to be fixed.
On Fri, Dec 20, 2019 at 1:11 PM Tibor Digana wrote:
> I want to review the closed issues as well i would like to come up with
> those which should be reopened to a certain release
I want to review the closed issues as well i would like to come up with
those which should be reopened to a certain release version.
I guess the release version should be set in such case.
We have also backlog version and that's the place where the issues should
be closed be the version has not
Please share the new query for this. It would give me fewer issues to look at.
By the way, I've chopped the original list from over four hundred to
just over two hundred, learned a lot about Maven in the process, found
one or two gems that have serious impact at my day job, and identified
one
One thing we should try going forward is be more ready to won't fix
and close bugs and RFEs we disagree with. I've seen several examples
where the comments indicate the maintainers did not agree with the
issue, but it still wasn't closed. E.g.
https://issues.apache.org/jira/browse/SUREFIRE-1227
I will exlude those. It does not makes sense to close/reopen again.
Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold:
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like we've been here before. Some of the bugs that were
autoclosed then were reopened and are now scheduled for autoclose
again. Any
Am 2019-12-13 um 16:08 schrieb Elliotte Rusty Harold:
NVM, I seem to have access now. I think I just needed to logout with
my old credentials and back in with the new ones.
Elliotte,
please go through the list and update those tickets you seen to be
addressible within a decent timeframe.
NVM, I seem to have access now. I think I just needed to logout with
my old credentials and back in with the new ones.
On Fri, Dec 13, 2019 at 9:56 AM Elliotte Rusty Harold
wrote:
>
> On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly
> wrote:
> > I think we have some crazy permissions that Brian
On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly
wrote:
> I think we have some crazy permissions that Brian manages. Ldap just fixes
> the account name to match across systems AIUI
>
That's probably true. As of an hour ago, I did not seem able to close issues.
--
Elliotte Rusty Harold
On Thu 12 Dec 2019 at 17:31, Robert Scholte wrote:
> IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do
> this anymore. All should be in place by now.
>
I think we have some crazy permissions that Brian manages. Ldap just fixes
the account name to match across systems AIUI
IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do this
anymore. All should be in place by now.
thanks,
Robert
On 12-12-2019 15:20:24, Stephen Connolly
wrote:
On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold
wrote:
> On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold
wrote:
> On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
> >
> > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > > Please don't. There are certainly some real and important issues in
> > > there. More importantly, users spent a
On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
>
> Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > Please don't. There are certainly some real and important issues in
> > there. More importantly, users spent a great deal of effort and time
> > to file those. Bulk closing them
Take your time, you have at least three weeks.
Am 2019-12-08 um 18:23 schrieb Tibor Digana:
Hi Michael,
What's up :-)
Thx for making the list of issues.
Pls give me one day to see it completely. I will get back to you tomorrow.
Cheers
Tibor17
On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty
Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
Please don't. There are certainly some real and important issues in
there. More importantly, users spent a great deal of effort and time
to file those. Bulk closing them tells those users we don't value
their feedback or effort. It is useful
Hi Michael,
What's up :-)
Thx for making the list of issues.
Pls give me one day to see it completely. I will get back to you tomorrow.
Cheers
Tibor17
On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty Harold
wrote:
> Please don't. There are certainly some real and important issues in
> there.
Please don't. There are certainly some real and important issues in
there. More importantly, users spent a great deal of effort and time
to file those. Bulk closing them tells those users we don't value
their feedback or effort. It is useful to triage these issues and
consider them individually.
Am 2019-12-08 um 13:55 schrieb Maarten Mulders:
Hi Michael,
Great initiative. After logging in to JIRA, accessing your link shows
"The requested filter doesn't exist or is private."
This means I'm not able to verify whether there are issues in that list
that are valid for me.
Is there
Hi Michael,
Great initiative. After logging in to JIRA, accessing your link shows
"The requested filter doesn't exist or is private."
This means I'm not able to verify whether there are issues in that list
that are valid for me.
Is there another way to find those issues?
Cheers,
Maarten
On
Hi folks,
after at least one year of silence, I'd like to perform another JIRA
issue cleanup for issues which have been not touched for more than three
years.
Query:
21 matches
Mail list logo
