You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Paulo Motta <pa...@gmail.com> on 2021/03/21 22:05:45 UTC
[DISCUSS] Improve JIRA and Github ticket higyene
Hi everyone,
While triaging tickets for Google Summer of Code I went through dozens of
invalid and stale tickets on JIRA that were still open. In addition to
other issues, this makes it harder for new contributors to identify valid
tickets to work on. Ideally any ticket that was triaged by a contributor
should be good to work on, but this is not the current state of our JIRA.
I was wondering if we should adopt some strategy to auto-close JIRA tickets
and/or GitHub PRs after a period of inactivity and wanted to bring this
discussion to the community. One downside of this is that valid tickets
might be auto-closed, but we could use a few strategies to mitigate that:
a) use a long enough period (ie. 2 years), if an issue wasn't worked on
within this period then it's probably not relevant enough and can be
abandoned. This would already get rid of a large backlog of abandoned
tickets dating back to as early as 2014 (or even earlier).
b) if the issue hasn't been worked on for a large period but the community
still finds it relevant, add some tag to prevent that ticket from being
auto-closed.
I think that this is something that is pretty easy to fix and will make our
ticket tracking more reliable and easier for new contributors to get
started, especially in the post 4.0 world.
Please let me know what do you think,
Paulo
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Berenguer Blasi <be...@gmail.com>.
Just suggested using jira filters subscription as a low investment
alternative for the POC. Nice initiative imo.
On 10/4/21 23:18, Joshua McKenzie wrote:
> One brief note but otherwise LGTM as a starting point for trying something
> out.
>
> ~Josh
>
> On Sat, Apr 10, 2021 at 11:34 AM Paulo Motta <pa...@gmail.com>
> wrote:
>
>> Hi folks,
>>
>> I consolidated the proposal previously discussed on how to improve JIRA
>> ticket hygiene and visibility on this document [1]. For now I focused on
>> JIRA to keep things simple, once we have that done we can do the github
>> part.
>>
>> I would greatly appreciate the community's feedback and suggestions on this
>> proposal.
>>
>> Cheers,
>>
>> Paulo
>>
>> [1] -
>>
>> https://docs.google.com/document/d/1PDFoHVq_KvZZdMaXJ4HYdpPwaU_5748U-gOCq7Slbao/edit
>>
>> Em qua., 24 de mar. de 2021 às 22:04, Paulo Motta <
>> pauloricardomg@gmail.com>
>> escreveu:
>>
>>> Great, thanks for the feedback!
>>>
>>> I will consolidate this discussion on a more concrete proposal and share
>>> with the community for validation when I have it.
>>>
>>> In the meantime if anyone has additional suggestions feel free to chime
>> in.
>>> Em qua., 24 de mar. de 2021 às 06:23, Benjamin Lerer <b....@gmail.com>
>>> escreveu:
>>>
>>>> The proposal sounds good to me.
>>>>
>>>> Thanks for looking into this problem Paulo.
>>>>
>>>> Le mer. 24 mars 2021 à 09:05, Mick Semb Wever <mc...@apache.org> a écrit
>> :
>>>>>> What do you think about this alternative proposal?
>>>>>>
>>>>>
>>>>> Perfect! All my concerns are addressed, thanks for taking the time
>>>> Paulo.
>>>>> Quite excited now at the prospect of what this undertaking means for
>> us.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Joshua McKenzie <jm...@apache.org>.
One brief note but otherwise LGTM as a starting point for trying something
out.
~Josh
On Sat, Apr 10, 2021 at 11:34 AM Paulo Motta <pa...@gmail.com>
wrote:
> Hi folks,
>
> I consolidated the proposal previously discussed on how to improve JIRA
> ticket hygiene and visibility on this document [1]. For now I focused on
> JIRA to keep things simple, once we have that done we can do the github
> part.
>
> I would greatly appreciate the community's feedback and suggestions on this
> proposal.
>
> Cheers,
>
> Paulo
>
> [1] -
>
> https://docs.google.com/document/d/1PDFoHVq_KvZZdMaXJ4HYdpPwaU_5748U-gOCq7Slbao/edit
>
> Em qua., 24 de mar. de 2021 às 22:04, Paulo Motta <
> pauloricardomg@gmail.com>
> escreveu:
>
> > Great, thanks for the feedback!
> >
> > I will consolidate this discussion on a more concrete proposal and share
> > with the community for validation when I have it.
> >
> > In the meantime if anyone has additional suggestions feel free to chime
> in.
> >
> > Em qua., 24 de mar. de 2021 às 06:23, Benjamin Lerer <b....@gmail.com>
> > escreveu:
> >
> >> The proposal sounds good to me.
> >>
> >> Thanks for looking into this problem Paulo.
> >>
> >> Le mer. 24 mars 2021 à 09:05, Mick Semb Wever <mc...@apache.org> a écrit
> :
> >>
> >> > >
> >> > > What do you think about this alternative proposal?
> >> > >
> >> >
> >> >
> >> > Perfect! All my concerns are addressed, thanks for taking the time
> >> Paulo.
> >> >
> >> > Quite excited now at the prospect of what this undertaking means for
> us.
> >> >
> >>
> >
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Paulo Motta <pa...@gmail.com>.
Hi folks,
I consolidated the proposal previously discussed on how to improve JIRA
ticket hygiene and visibility on this document [1]. For now I focused on
JIRA to keep things simple, once we have that done we can do the github
part.
I would greatly appreciate the community's feedback and suggestions on this
proposal.
Cheers,
Paulo
[1] -
https://docs.google.com/document/d/1PDFoHVq_KvZZdMaXJ4HYdpPwaU_5748U-gOCq7Slbao/edit
Em qua., 24 de mar. de 2021 às 22:04, Paulo Motta <pa...@gmail.com>
escreveu:
> Great, thanks for the feedback!
>
> I will consolidate this discussion on a more concrete proposal and share
> with the community for validation when I have it.
>
> In the meantime if anyone has additional suggestions feel free to chime in.
>
> Em qua., 24 de mar. de 2021 às 06:23, Benjamin Lerer <b....@gmail.com>
> escreveu:
>
>> The proposal sounds good to me.
>>
>> Thanks for looking into this problem Paulo.
>>
>> Le mer. 24 mars 2021 à 09:05, Mick Semb Wever <mc...@apache.org> a écrit :
>>
>> > >
>> > > What do you think about this alternative proposal?
>> > >
>> >
>> >
>> > Perfect! All my concerns are addressed, thanks for taking the time
>> Paulo.
>> >
>> > Quite excited now at the prospect of what this undertaking means for us.
>> >
>>
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Paulo Motta <pa...@gmail.com>.
Great, thanks for the feedback!
I will consolidate this discussion on a more concrete proposal and share
with the community for validation when I have it.
In the meantime if anyone has additional suggestions feel free to chime in.
Em qua., 24 de mar. de 2021 às 06:23, Benjamin Lerer <b....@gmail.com>
escreveu:
> The proposal sounds good to me.
>
> Thanks for looking into this problem Paulo.
>
> Le mer. 24 mars 2021 à 09:05, Mick Semb Wever <mc...@apache.org> a écrit :
>
> > >
> > > What do you think about this alternative proposal?
> > >
> >
> >
> > Perfect! All my concerns are addressed, thanks for taking the time Paulo.
> >
> > Quite excited now at the prospect of what this undertaking means for us.
> >
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Benjamin Lerer <b....@gmail.com>.
The proposal sounds good to me.
Thanks for looking into this problem Paulo.
Le mer. 24 mars 2021 à 09:05, Mick Semb Wever <mc...@apache.org> a écrit :
> >
> > What do you think about this alternative proposal?
> >
>
>
> Perfect! All my concerns are addressed, thanks for taking the time Paulo.
>
> Quite excited now at the prospect of what this undertaking means for us.
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Mick Semb Wever <mc...@apache.org>.
>
> What do you think about this alternative proposal?
>
Perfect! All my concerns are addressed, thanks for taking the time Paulo.
Quite excited now at the prospect of what this undertaking means for us.
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Paulo Motta <pa...@gmail.com>.
> Though in practice, i'm wondering if the second phase should be done
carefully/manually the first couple of times to make sure we're getting it
right. I can think of a number of reasons where it might fail and am not
confident we'll anticipate everything.
Yeah I think it makes sense to start with a manual second phase to build
confidence in the automation, evaluate and then automatize it if it works
as expected.
If there are no objections I will draft a more concrete proposal for this
automation to validate with the community.
> Issues like RAMP, EPaxos, Expressive Consistency Levels, shouldn't be
closed just because they haven't been touched for 4+ years.
Having them open is valid so long as the idea is valid on Cassandra. And
folk shouldn't be having to save them twice a year when the jira automation
bot runs…
100% agree, my intent here is not to close tickets that have been inactive
in 5 years that are still relevant, but rather to have a consistent
workflow to prune old tickets from the backlog that are no longer valid or
relevant.
The originally proposed approach was "opt-out", that is, inactive tickets
not "touched" within 6 months would be auto-closed, but this is risky as we
could auto-close potentially relevant tickets.
How about having an "opt-in" approach instead, where tickets inactive for 5
years would be tagged with "needs-retriage" and added to a new "Needs
retriage" list? This would allow volunteers to go to this list to retriage
and manually close old tickets according to a well defined and documented
procedure.
We could have a "no-retriage-neeeded" tag to skip retriaging for "blue sky
ideas" like RAMP, EPaxos, Expressive Consistency Levels.
I did a quick manual dry-run of this approach on tickets older than 5 years
[1] (available here [2]), and around 50% of the tickets can be closed on
the sample I used.
What do you think about this alternative proposal?
[1]
https://www.google.com/url?q=https://issues.apache.org/jira/browse/CASSANDRA-11407?jql%3Dproject%2520%253D%2520cassandra%2520AND%2520resolution%2520%253D%2520unresolved%2520AND%2520created%2520%253C%2520%25222016-03-23%2522%2520ORDER%2520BY%2520created%2520DESC&sa=D&source=editors&ust=1616550373374000&usg=AFQjCNFsDx1IkQZREC4vLjFG35np5Vqqag
[2]
https://docs.google.com/spreadsheets/d/1lnM4ez_w92JmoJj0VPmnxY17agG_MUFDhyLAnFFVv4M/edit?usp=sharing
Em ter., 23 de mar. de 2021 às 04:41, Mick Semb Wever <mc...@apache.org>
escreveu:
> but can't we make list maintenance via JIRA
> > Automation [1] instead of requiring manual maintenance?
> >
>
>
> In principle i'm +1 to most of the two phase approaches you suggest. The
> labelling of tickets and warning of a pending close/change is a good
> approach. And I'm all for automating everything that can be.
>
> Though in practice, i'm wondering if the second phase should be done
> carefully/manually the first couple of times to make sure we're getting it
> right. I can think of a number of reasons where it might fail and am not
> confident we'll anticipate everything.
>
> And, I don't think the second phase should apply to 'Open Issue', see
> below.
>
>
> A task that hasn't been updated on for 4-5 years will likely never be
> > worked again, so why should they remain open polluting the backlog?
>
>
>
> OSS jira is as much a knowledge base as it is the currently active
> contributor's backlog.
>
> Issues like RAMP, EPaxos, Expressive Consistency Levels, shouldn't be
> closed just because they haven't been touched for 4+ years.
> Having them open is valid so long as the idea is valid on Cassandra. And
> folk shouldn't be having to save them twice a year when the jira automation
> bot runs…
>
> The Open Issues list is a way of seeing what Cassandra is potentially
> capable of, i.e. its possible horizon. These tickets can contain lots of
> valuable information, even for next-generation ideas that supersede them
> (which would close them out). And even trivial bugs, so long as they are
> still true, shouldn't be closed just because they've existed untouched for
> 4 years. Folk having to crawl through closed tickets to undercover valid
> ideas, or valid bugs, in our knowledge base doesn't sit right for me.
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Mick Semb Wever <mc...@apache.org>.
but can't we make list maintenance via JIRA
> Automation [1] instead of requiring manual maintenance?
>
In principle i'm +1 to most of the two phase approaches you suggest. The
labelling of tickets and warning of a pending close/change is a good
approach. And I'm all for automating everything that can be.
Though in practice, i'm wondering if the second phase should be done
carefully/manually the first couple of times to make sure we're getting it
right. I can think of a number of reasons where it might fail and am not
confident we'll anticipate everything.
And, I don't think the second phase should apply to 'Open Issue', see below.
A task that hasn't been updated on for 4-5 years will likely never be
> worked again, so why should they remain open polluting the backlog?
OSS jira is as much a knowledge base as it is the currently active
contributor's backlog.
Issues like RAMP, EPaxos, Expressive Consistency Levels, shouldn't be
closed just because they haven't been touched for 4+ years.
Having them open is valid so long as the idea is valid on Cassandra. And
folk shouldn't be having to save them twice a year when the jira automation
bot runs…
The Open Issues list is a way of seeing what Cassandra is potentially
capable of, i.e. its possible horizon. These tickets can contain lots of
valuable information, even for next-generation ideas that supersede them
(which would close them out). And even trivial bugs, so long as they are
still true, shouldn't be closed just because they've existed untouched for
4 years. Folk having to crawl through closed tickets to undercover valid
ideas, or valid bugs, in our knowledge base doesn't sit right for me.
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Paulo Motta <pa...@gmail.com>.
Thanks for contributing to the discussion Mick.
I like the idea of having handy lists for "Triage", "Open", "Patch
Available", "Reviewed Once" to give more visibility and transparency to the
ticket triaging/review process, but can't we make list maintenance via JIRA
Automation [1] instead of requiring manual maintenance?
For example:
* "In Progress" (is it still? or should be returned to Open, or closed out)
* Ticket has been in progress for more than 6 months? Add tag
"stale-in-progress" and a message saying that the ticket will be set to
open in 1 month if tag is not removed.
* Ticket has tag "stale-in-progress" for more than 1 month? Set state to
Open.
* "In Review" (should they be returned to 'in progress', or has the
reviewer gone MIA and it needs to go back to 'Patch Available')
* Ticket has been in review for more than 3 months ? Add tag
"stale-in-review" and message saying that the ticket will be set to "patch
available" in 1 month if tag is not removed.
* Ticket has tag "stale-in-review" for more than 1 month? Set state to
Patch Available.
In the same spirit, we could have a similar workflow for getting rid of
abandoned tasks from the backlog:
* Ticket without update for more than 4 years (debatable duration)? Add tag
"to-be-abandoned" and message:
* "Hey buddy, do you think this task is still important? If so, please
remove the tag 'to-be-abadoned', otherwise I will close this ticket in 6
months".
* Ticket has "to-be-abandoned" tag for more than 6 months? Close with
"Abandoned" state
A task that hasn't been updated on for 4-5 years will likely never be
worked again, so why should they remain open polluting the backlog? We will
give people a grace period of 6 months to "touch" the issue if they want to
renew the TTL for 4 more years, which should be sufficient to "save"
relevant tickets from the guillotine. And even after they're abandoned they
can always be "reopened" if necessary.
Does this auto-closing strategy make you less uncomfortable? If not, do you
mind elaborating why? I'd also love to hear others opinions on this.
+1 to the Github workflow suggestions.
[1] - https://www.atlassian.com/software/jira/features/automation
Em seg., 22 de mar. de 2021 às 12:33, Mick Semb Wever <mc...@apache.org>
escreveu:
> Throwing my thoughts out there on this.
>
>
>
> > A much harder
> > objective is to ensure that all "Patch Available" tickets are reviewed
> in a
> > timely manner. However the current backlog of abandoned PA tickets is
> also
> > large and we need to clean it to "start fresh" so the auto-close proposal
> > would also help here.
> >
>
>
> We have this list:
> https://cwiki.apache.org/confluence/display/CASSANDRA/Patch+Available
>
> Post 4.0 it would help with a way to incentivise reviews (by anyone) and a
> committer's involvement.
>
> The list is helpful for jumping in and helping out, but some things missing
> that would greatly help the flow of things is…
>
> - when has the existing reviewer(s) gone MIA and the ticket stale,
> - when has one non-committer reviewed it and it is only waiting on a
> committer to jump in,
> - when it is in action, or intentionally parked, and not needing anyone new
> involved,
> - when has communication gone stale, or the ticket been left in the wrong
> state.
>
> That is, to have lists like this for
> - "Triage" (Needs to be triaged)
> - "Open" (Needs to be implemented)
> - "Patch Available" (Needs to be reviewed)
> - "Reviewed Once" (Needs a second reviewer)
>
> will help a lot, making it easier for folk to jump in when they have a few
> free hours…
>
> But for each list we also need some project documentation on "list
> maintenance". The process for maintaining these lists should be as simple
> and standard and repeatable as possible, by anyone (including
> non-committers). List maintenance is not about triaging, implementing, or
> reviewing, but solely about tackling ticket hygiene. Having it documented
> so it's not tribal knowledge and anyone can step in and do it with
> confidence would open up the process for more people. Do we have any takers
> for creating a skeleton of such documentation?
>
> I imagine that list maintenance would also include the following lists:
> - "In Progress" (is it still? or should be returned to Open, or closed
> out)
> - "In Review" (should they be returned to 'in progress', or has the
> reviewer gone MIA and it needs to go back to 'Patch Available')
>
>
> I agree that auto-closing tickets by itself will not fix the larger issue
> > mentioned before, but it's just an initial step to "clean the past" so we
> > have an actionable backlog after the 4.0 ticket freeze is over.
>
>
>
> I'm not comfortable with automatically closing tickets, or the idea we can
> just "start with a clean slate".
> But I think we may find automatic reminders/comments on tickets helps make
> list maintenance quick and simple.
>
> While GitHub issues are currently completely disabled from our
> repositories, GitHub PRs on the Cassandra repository should be closed if
> they don't reference a jira ticket, or if they reference a closed ticket.
>
> The use of PRs on builds, dtests, and the website, without a corresponding
> jira ticket is worth a discussion. I'm in favour of small changes on these
> repositories being tackled with just PRs.
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Mick Semb Wever <mc...@apache.org>.
Throwing my thoughts out there on this.
> A much harder
> objective is to ensure that all "Patch Available" tickets are reviewed in a
> timely manner. However the current backlog of abandoned PA tickets is also
> large and we need to clean it to "start fresh" so the auto-close proposal
> would also help here.
>
We have this list:
https://cwiki.apache.org/confluence/display/CASSANDRA/Patch+Available
Post 4.0 it would help with a way to incentivise reviews (by anyone) and a
committer's involvement.
The list is helpful for jumping in and helping out, but some things missing
that would greatly help the flow of things is…
- when has the existing reviewer(s) gone MIA and the ticket stale,
- when has one non-committer reviewed it and it is only waiting on a
committer to jump in,
- when it is in action, or intentionally parked, and not needing anyone new
involved,
- when has communication gone stale, or the ticket been left in the wrong
state.
That is, to have lists like this for
- "Triage" (Needs to be triaged)
- "Open" (Needs to be implemented)
- "Patch Available" (Needs to be reviewed)
- "Reviewed Once" (Needs a second reviewer)
will help a lot, making it easier for folk to jump in when they have a few
free hours…
But for each list we also need some project documentation on "list
maintenance". The process for maintaining these lists should be as simple
and standard and repeatable as possible, by anyone (including
non-committers). List maintenance is not about triaging, implementing, or
reviewing, but solely about tackling ticket hygiene. Having it documented
so it's not tribal knowledge and anyone can step in and do it with
confidence would open up the process for more people. Do we have any takers
for creating a skeleton of such documentation?
I imagine that list maintenance would also include the following lists:
- "In Progress" (is it still? or should be returned to Open, or closed out)
- "In Review" (should they be returned to 'in progress', or has the
reviewer gone MIA and it needs to go back to 'Patch Available')
I agree that auto-closing tickets by itself will not fix the larger issue
> mentioned before, but it's just an initial step to "clean the past" so we
> have an actionable backlog after the 4.0 ticket freeze is over.
I'm not comfortable with automatically closing tickets, or the idea we can
just "start with a clean slate".
But I think we may find automatic reminders/comments on tickets helps make
list maintenance quick and simple.
While GitHub issues are currently completely disabled from our
repositories, GitHub PRs on the Cassandra repository should be closed if
they don't reference a jira ticket, or if they reference a closed ticket.
The use of PRs on builds, dtests, and the website, without a corresponding
jira ticket is worth a discussion. I'm in favour of small changes on these
repositories being tackled with just PRs.
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Paulo Motta <pa...@gmail.com>.
Thanks for your feedback Stefan!
I totally agree that an important reason for tickets being abandoned is
that committers don't have the bandwidth to review these tickets since they
are focusing on larger-impact tasks. Missing these contributions is very
bad for the project not only because we lose the actual minor fixes and
improvements that make the project more stable and usable, but also because
we don't value the time the people took to the make contribution by
properly reviewing them, so they are not encouraged to return and make new
contributions, so we lose in the long run by not attracting new
contributors which could in turn increase the project contributor's pool.
I agree that auto-closing tickets by itself will not fix the larger issue
mentioned before, but it's just an initial step to "clean the past" so we
have an actionable backlog after the 4.0 ticket freeze is over. I believe
the addition of the "Triage Needed" state helps a lot to filter valid
tickets as they are filled, since in the past any opened ticket would go
directly into "open" state and pollute the backlog with invalid tickets
that bypassed triaging.
My initial objective is to ensure that the "Triage Needed" list is small,
and the "Open" tickets can be worked on, which is not the current state but
it's pretty simple to achieve with the auto-close proposal. A much harder
objective is to ensure that all "Patch Available" tickets are reviewed in a
timely manner. However the current backlog of abandoned PA tickets is also
large and we need to clean it to "start fresh" so the auto-close proposal
would also help here.
While I recognize the importance of implementing an strategy to avoid
useful contributions from being abandoned and I'm personally committed to
improving this, I think this is a much lengthier discussion and wanted to
limit this thread to the practical objective of cleaning up the current
JIRA state, since I believe this will help regardless of the strategy we
choose to address the issue of preventing the tickets from being abandoned
in the first place.
Em seg., 22 de mar. de 2021 às 06:26, Stefan Miklosovic <
stefan.miklosovic@instaclustr.com> escreveu:
> Hi Paulo,
>
> it might seem as me complaining but that is not the case here so just
> hear me out please.
>
> I think that the primary reason for tickets not being resolved / they
> are abandoned / they are not worked on anymore is not the fact that
> they are just "forgotten" but I believe that it is also because after
> spending some time around the project, one just feels what ticket has
> any reasonable chance to get through and be eventually committed or if
> that ticket is just not too important after all (from time-management
> point of view) and it just does not make sense to work on it because
> the amount of time spent on it to chase committers to look at it is
> just not worth it which is quite sad but understandable. I know about
> a couple of tickets I would like to see merged but I just do not
> bother because I am not a committer myself and begging people for a
> couple weeks to look at some minor stuff is just a waste of time for
> everybody. But it does not mean that such a ticket is "useless". It is
> more about people not having any more bandwidth to look at them and so
> on ...
>
> Minor or low-hanging fruit tickets are easy to work on and they are
> usually the entry point for new contributors but those who do have
> commit rights are not too often impressed and it stays under the
> radar, it is a chicken-egg problem and eventually the project as a
> whole loses, contributors are often discouraged and minor fixes sum
> over time to quite a lot of changes which makes the difference but
> they are not there ...
>
> Hence while I guess some solutions you propose are sound, it still
> does not prevent valid tickets to be abandoned and forgotten
> completely. I would yet like to see what mechanism would be put in
> action to decide what ticket is relevant or not after being not worked
> on for a substantial amount of time.
>
> Regards
>
> On Sun, 21 Mar 2021 at 23:06, Paulo Motta <pa...@gmail.com>
> wrote:
> >
> > Hi everyone,
> >
> > While triaging tickets for Google Summer of Code I went through dozens of
> > invalid and stale tickets on JIRA that were still open. In addition to
> > other issues, this makes it harder for new contributors to identify valid
> > tickets to work on. Ideally any ticket that was triaged by a contributor
> > should be good to work on, but this is not the current state of our JIRA.
> >
> > I was wondering if we should adopt some strategy to auto-close JIRA
> tickets
> > and/or GitHub PRs after a period of inactivity and wanted to bring this
> > discussion to the community. One downside of this is that valid tickets
> > might be auto-closed, but we could use a few strategies to mitigate that:
> > a) use a long enough period (ie. 2 years), if an issue wasn't worked on
> > within this period then it's probably not relevant enough and can be
> > abandoned. This would already get rid of a large backlog of abandoned
> > tickets dating back to as early as 2014 (or even earlier).
> > b) if the issue hasn't been worked on for a large period but the
> community
> > still finds it relevant, add some tag to prevent that ticket from being
> > auto-closed.
> >
> > I think that this is something that is pretty easy to fix and will make
> our
> > ticket tracking more reliable and easier for new contributors to get
> > started, especially in the post 4.0 world.
> >
> > Please let me know what do you think,
> >
> > Paulo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [DISCUSS] Improve JIRA and Github ticket higyene
Posted by Stefan Miklosovic <st...@instaclustr.com>.
Hi Paulo,
it might seem as me complaining but that is not the case here so just
hear me out please.
I think that the primary reason for tickets not being resolved / they
are abandoned / they are not worked on anymore is not the fact that
they are just "forgotten" but I believe that it is also because after
spending some time around the project, one just feels what ticket has
any reasonable chance to get through and be eventually committed or if
that ticket is just not too important after all (from time-management
point of view) and it just does not make sense to work on it because
the amount of time spent on it to chase committers to look at it is
just not worth it which is quite sad but understandable. I know about
a couple of tickets I would like to see merged but I just do not
bother because I am not a committer myself and begging people for a
couple weeks to look at some minor stuff is just a waste of time for
everybody. But it does not mean that such a ticket is "useless". It is
more about people not having any more bandwidth to look at them and so
on ...
Minor or low-hanging fruit tickets are easy to work on and they are
usually the entry point for new contributors but those who do have
commit rights are not too often impressed and it stays under the
radar, it is a chicken-egg problem and eventually the project as a
whole loses, contributors are often discouraged and minor fixes sum
over time to quite a lot of changes which makes the difference but
they are not there ...
Hence while I guess some solutions you propose are sound, it still
does not prevent valid tickets to be abandoned and forgotten
completely. I would yet like to see what mechanism would be put in
action to decide what ticket is relevant or not after being not worked
on for a substantial amount of time.
Regards
On Sun, 21 Mar 2021 at 23:06, Paulo Motta <pa...@gmail.com> wrote:
>
> Hi everyone,
>
> While triaging tickets for Google Summer of Code I went through dozens of
> invalid and stale tickets on JIRA that were still open. In addition to
> other issues, this makes it harder for new contributors to identify valid
> tickets to work on. Ideally any ticket that was triaged by a contributor
> should be good to work on, but this is not the current state of our JIRA.
>
> I was wondering if we should adopt some strategy to auto-close JIRA tickets
> and/or GitHub PRs after a period of inactivity and wanted to bring this
> discussion to the community. One downside of this is that valid tickets
> might be auto-closed, but we could use a few strategies to mitigate that:
> a) use a long enough period (ie. 2 years), if an issue wasn't worked on
> within this period then it's probably not relevant enough and can be
> abandoned. This would already get rid of a large backlog of abandoned
> tickets dating back to as early as 2014 (or even earlier).
> b) if the issue hasn't been worked on for a large period but the community
> still finds it relevant, add some tag to prevent that ticket from being
> auto-closed.
>
> I think that this is something that is pretty easy to fix and will make our
> ticket tracking more reliable and easier for new contributors to get
> started, especially in the post 4.0 world.
>
> Please let me know what do you think,
>
> Paulo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org