You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Paul Burba <pt...@gmail.com> on 2012/12/19 16:55:52 UTC
Request: Issue Triage Cleanup
One of the regular tasks in preparation for a new release is review
all outstanding issues that may block the release, e.g. "Issue triage
-- Review open issues for the 1.8.0, 1.8-consider, and 1.7.x,
milestones." Obviously when somebody marks an issue with milestone of
1.8.0 this indicates the issue should be addressed before we release.
This is all well and good, but what about the large number of issues
that simply have no target milestone? I don't mean milestones of
'unscheduled', 'nonblocking', of 'blue-sky', but those with the
default of '---'? While the bulk of these are unlikely to be blockers
for the next release, we really have no way of knowing. Currently 228
of the 728 open issues in our tracker have target milestones of '---'.
My request is this: In the lead up to branching 1.8 please try to find
some time to review any issues you've filed (or are assigned to you)
that have the '---' milestone and set an appropriate new milestone.
This can be done easily via http://subversion.tigris.org/issues/query.cgi
E.g. http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=---&email1=cmpilato&emailtype1=exact&emailassigned_to1=1&emailreporter1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=fulltext&long_desc=&long_desc_type=fulltext&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query
This isn't intended merely as an exercise in OCD, but rather a
reasonable step to ensure no regressions slip between the cracks.
Thanks all,
--
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba
Re: Request: Issue Triage Cleanup
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 12/19/2012 11:48 AM, Paul Burba wrote:
> Not sure about 'blue-sky'. There are only 16 open issues with this
> milestone. I always took it mean something along the lines of 'not
> going to happen before 2.0 or without a massive amount of work for
> limited gain', but I don't know that there is any official definition.
2.0-consider is for 2.0 stuff.
These days I tend to think of blue-sky as more like, "if one of us wins the
tri-state lottery, pays for twice as many developers to work on exactly this
problem, and bribes all the users to not complain when we break
compatibility promises to make it all happen ... and if it never happens,
nobody really cares." Okay, maybe that's a bit much, but...
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Re: Request: Issue Triage Cleanup
Posted by Paul Burba <pt...@gmail.com>.
On Wed, Dec 19, 2012 at 11:39 AM, Philip Martin
<ph...@wandisco.com> wrote:
>>> I don't mean milestones of 'unscheduled', 'nonblocking', of 'blue-sky',
>
> Do those milestones have an agreed meaning? What is the difference?
My understanding of unscheduled and nonblocking as is per
http://subversion.tigris.org/issue-tracker.html
[[[
When an issue is first filed, it automatically goes in the "---"
target milestone, which indicates that the issue has not yet been
processed. A developer will examine it and maybe talk to other
developers, then estimate the bug's severity, the effort required to
fix it, and schedule it in a numbered milestone, for example 1.1. (Or
they may put it the unscheduled or nonblocking milestone, if they
consider it tolerable for all currently planned releases.)
An issue filed in unscheduled might still get fixed soon, if some
committer decides they want it done. Putting it in unscheduled merely
means it hasn't been scheduled for any particular release yet. The
nonblocking milestone, on the other hand, means that we do not
anticipate ever scheduling the issue for a particular release. This
also does not mean the issue will never be fixed; it merely means that
we don't plan to block any release on it.
]]]
Not sure about 'blue-sky'. There are only 16 open issues with this
milestone. I always took it mean something along the lines of 'not
going to happen before 2.0 or without a massive amount of work for
limited gain', but I don't know that there is any official definition.
> --
> Certified & Supported Apache Subversion Downloads:
> http://www.wandisco.com/subversion/download
--
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba
Re: Request: Issue Triage Cleanup
Posted by Philip Martin <ph...@wandisco.com>.
>> I don't mean milestones of 'unscheduled', 'nonblocking', of 'blue-sky',
Do those milestones have an agreed meaning? What is the difference?
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: Request: Issue Triage Cleanup
Posted by Mark Phippard <ma...@gmail.com>.
I think if you are logged in to tigris, this URL will show you all the
issues you have entered:
http://subversion.tigris.org/issues/buglist.cgi?cmdtype=runuserdefault
If you click on Change Columns you can add the Target Milestone
column. This makes it easy to see if you have entered any issues
where a milestone was not added.
Mark
On Wed, Dec 19, 2012 at 10:55 AM, Paul Burba <pt...@gmail.com> wrote:
> One of the regular tasks in preparation for a new release is review
> all outstanding issues that may block the release, e.g. "Issue triage
> -- Review open issues for the 1.8.0, 1.8-consider, and 1.7.x,
> milestones." Obviously when somebody marks an issue with milestone of
> 1.8.0 this indicates the issue should be addressed before we release.
>
> This is all well and good, but what about the large number of issues
> that simply have no target milestone? I don't mean milestones of
> 'unscheduled', 'nonblocking', of 'blue-sky', but those with the
> default of '---'? While the bulk of these are unlikely to be blockers
> for the next release, we really have no way of knowing. Currently 228
> of the 728 open issues in our tracker have target milestones of '---'.
>
> My request is this: In the lead up to branching 1.8 please try to find
> some time to review any issues you've filed (or are assigned to you)
> that have the '---' milestone and set an appropriate new milestone.
>
> This can be done easily via http://subversion.tigris.org/issues/query.cgi
>
> E.g. http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=---&email1=cmpilato&emailtype1=exact&emailassigned_to1=1&emailreporter1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=fulltext&long_desc=&long_desc_type=fulltext&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query
>
> This isn't intended merely as an exercise in OCD, but rather a
> reasonable step to ensure no regressions slip between the cracks.
>
> Thanks all,
>
> --
> Paul T. Burba
> CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
> Skype: ptburba
--
Thanks
Mark Phippard
http://markphip.blogspot.com/