[Proposal] Make "Affects Version" field mandatory for new tickets with "Bug" issue type in JIRA
The dialog window that opens in the Geode JIRA when creating a new ticket
currently has three mandatory fields; Project, Issue Type and Summary, which
are necessary for every ticket. There are also three optional fields for
Component, Description and Affects Version, since there are cases when a ticket
can be created without needing these details ("Affects Version" has no clear
meaning for tickets with the "New Feature" issue type, for example).
However, in the case of tickets with the "Bug" issue type, I feel that an
"Affects Version" should be a mandatory field, as the version affected by a bug
is vital information when it comes to triaging and fixing bugs, and I
frequently see tickets filed with this field not filled in. I'd like to propose
that we change this field to be mandatory for new Bug tickets. Please let me
know what you think about this idea, or if there are issues or complications
that I've missed.
Donal
Re: [PROPOSAL] re-cut support/1.15
Hello Geode Community, counting the labels in Jira I see: May 6: 1 needsTriage and 2 blocks-1.15.0. May 20: 0 needsTriage and 3 blocks-1.15.0. Looks like some progress. Please continue to use the above labels to raise any issues. -1.15.0 Release Manager From: Owen Nichols Date: Monday, May 9, 2022 at 10:31 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] re-cut support/1.15 ** The support/1.15 branch has now been (re)cut and develop is now 1.16. ** Please use your best judgement in determining what to backport. PRs against support/1.15 are welcome (but optional!). Committers should merge their own PRs. If your backport will take some while, add the "blocks-1.15.0" label in Jira. From: Owen Nichols Date: Friday, May 6, 2022 at 10:47 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] re-cut support/1.15 Great news! I would be delighted to continue as Release Manager for 1.15.0. To track progress toward code-complete, I will monitor the "needsTriage" and "blocks-1.15.0" labels (for Affects Version = 1.15.0). Currently I see 1 needsTriage [1] and 2 blocks-1.15.0 [2]. [1] https://tinyurl.com/5h58766f [2] https://tinyurl.com/2p8bje4n From: Anthony Baker Date: Friday, May 6, 2022 at 10:19 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] annul support/1.15 Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties? @Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”). Thanks, Anthony > On Mar 16, 2022, at 2:12 PM, Owen Nichols wrote: > > Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 > a few weeks ago. I wonder if perhaps we cut the release branch prematurely? > I propose that we abandon this branch and focus on getting develop closer to > what we want to ship, then discuss re-cutting the branch. > > If this proposal is approved, I will archive support/1.15 as > support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all > Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering > would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut. > > Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar > 21. > > Thanks, > -Geode 1.15.0 Release Manager > >
Re: [Proposal] Make "Affects Version" field mandatory for new tickets with "Bug" issue type in JIRA
I think this is a great idea! I looked into this a while ago, but at the time
couldn't find a way to make a field required only for a certain ticket type
without additional, commercial extensions for JIRA.
From: Donal Evans
Sent: Thursday, May 26, 2022 10:09
To: dev@geode.apache.org
Subject: [Proposal] Make "Affects Version" field mandatory for new tickets with
"Bug" issue type in JIRA
⚠ External Email
The dialog window that opens in the Geode JIRA when creating a new ticket
currently has three mandatory fields; Project, Issue Type and Summary, which
are necessary for every ticket. There are also three optional fields for
Component, Description and Affects Version, since there are cases when a ticket
can be created without needing these details ("Affects Version" has no clear
meaning for tickets with the "New Feature" issue type, for example).
However, in the case of tickets with the "Bug" issue type, I feel that an
"Affects Version" should be a mandatory field, as the version affected by a bug
is vital information when it comes to triaging and fixing bugs, and I
frequently see tickets filed with this field not filled in. I'd like to propose
that we change this field to be mandatory for new Bug tickets. Please let me
know what you think about this idea, or if there are issues or complications
that I've missed.
Donal
⚠ External Email: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender.
Re: [Proposal] Make "Affects Version" field mandatory for new tickets with "Bug" issue type in JIRA
I think it is reasonable to “reject” bug reports that don’t include simple
things like “version” and “description”.
I agree, a bug report with the initially effected version filled in should be
marked as incomplete and the same should be said about the description field.
If there is not enough information in that field that explains what the bug is,
how it manifested itself then the bug report should be marked as incomplete and
the reporter of the issue should be notified to complete the ticket with the
relevant information.
From: Alexander Murmann
Date: Friday, May 27, 2022 at 4:37 AM
To: dev@geode.apache.org
Subject: Re: [Proposal] Make "Affects Version" field mandatory for new tickets
with "Bug" issue type in JIRA
⚠ External Email
I think this is a great idea! I looked into this a while ago, but at the time
couldn't find a way to make a field required only for a certain ticket type
without additional, commercial extensions for JIRA.
From: Donal Evans
Sent: Thursday, May 26, 2022 10:09
To: dev@geode.apache.org
Subject: [Proposal] Make "Affects Version" field mandatory for new tickets with
"Bug" issue type in JIRA
⚠ External Email
The dialog window that opens in the Geode JIRA when creating a new ticket
currently has three mandatory fields; Project, Issue Type and Summary, which
are necessary for every ticket. There are also three optional fields for
Component, Description and Affects Version, since there are cases when a ticket
can be created without needing these details ("Affects Version" has no clear
meaning for tickets with the "New Feature" issue type, for example).
However, in the case of tickets with the "Bug" issue type, I feel that an
"Affects Version" should be a mandatory field, as the version affected by a bug
is vital information when it comes to triaging and fixing bugs, and I
frequently see tickets filed with this field not filled in. I'd like to propose
that we change this field to be mandatory for new Bug tickets. Please let me
know what you think about this idea, or if there are issues or complications
that I've missed.
Donal
⚠ External Email: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender.
