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 <ptbu...@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/
