Anybody following issues@ would have seen a lot of traffic from me
today. I've been updating milestones to make it easier to document
which issues were fixed in 1.7.0. The basic workflow was:
* Get list of all issue closed since 1.6.x branch
* Remove issue listed as fixed in various versions of 1.6.x (per CHANGES)
* Check the remainder against the existing 1.7.0 list
* Update 1.7.0-labeled issues which have been resolved in previous releases
* Manually check each issue closed since 1.6.x, but not on 1.7.0 list
* If lacking a milestone, assign it to 1.7.0.
The following query will now give all the issues we believe to have
been fixed in 1.7.0, and will hopefully help in constructing CHANGES:
http://subversion.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&component=subversion&issue_status=RESOLVED&resolution=FIXED&target_milestone=1.7.0&email1=&emailtype1=exact&emailassigned_to1=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
(Note: we still have ~30 1.7.0-labeled issues which haven't been
closed or postponed yet.)
When closing issues in the 1.7.0 release process, please be sure to
milestone them correctly.
Thanks,
-Hyrum
Received on 2011-02-02 23:38:29 CET