Hello Petr, On Friday 19 December 2008 04:20, Petr Rockai wrote: > ... > 2) It would be nice to have nicely formatted list of issues fixed between 2.1.2 > and 2.2.0pre1. I suppose our Issue Manager (currently the hat is worn by > Thorkil) could produce such a list without too much hassle? Ideally, it'd > contain issue number, its title (summary) and possibly the author(s) of the > fix. Thanks!
I finally got around to doing something about this. It was not particularly clear how to proceed and I am not even done yet, but I would like someone to take a look and comment and also, perhaps, suggest ideas about how to finish the job. I will describe what I have done so far in detail in the following. This will also allow people to comment on the validity of what I did and, quite possibly, suggest better ways to do it. So here we go: 1. The bug tracker request http://bugs.darcs.net/issue?&@columns=id,title&@sort=-activity&@filter=status&status=testing,resolved-in-unstable,resolved-in-stable,resolved gave me a list of ids and titles for resolved issues in most-recently-changed-first order. For the purposes of this exercise, resolved means status = testing, resolved-in-unstable, resolved-in-stable, or resolved. The problem now becomes one of limiting this list in two ways: Only include what is actually in the branch-2.2 repository. And only include what is not already in 2.1.2. 2. The last question, eliminating what is already in 2.1.2, I have not really solved. I have simply cut off the list below the date (2008-Nov-17) on which 2.1.2 was tagged. This probably needs to be refined. But in any case, that left me with a list of about 30 issues. 3. I then ran over the output of darcs changes for the branch-2.2 repository (pulled around 2009-Jan-08 16.30 UTC) and tried to identify patches that resolved particular issues. In practice, I was only able use the "resolve issue..." patches for this, and the corresponding patches I marked with an initial "2.2" in the list. (As part of this activity, I identified 3 issues that needed to be resolved, so I did that and added them to the list.) 4. Then I ran over the output of darcs pull --dry-run -a http://darcs.net for the branch-2.2 repository and similarly identified resolved issues. The identified issues I marked with an initial "unstable" indicating that they were in unstable, but not in the branch-2.2 repository. For convenience, I separated the resulting list in its three parts: "unstable", "2.2", and all the rest. Here it is: unstable 1279 ui bug: whatsnew dir => WARNING! dir does not exist! unstable 1302 fix update_roundup.pl re "resolved" status unstable 1206 English.hs (Numbered) is usually called "Countable" unstable 1285 cabal clean should remove cabal tests' intermediaries unstable 948 list in darcsman.hs/man_organizer duplicates Darcs.TheCommands.command_control_list 2.2 1223 sporadic init.sh test failure (2.1.1rc2+472) 2.2 525 amend-record => darcs patches show duplicate additions 2.2 1247 make TAGS is broken 2.2 1273 renameFile: does not exist (No such file or directory) 2.2 1165 get should print last gotten tag 2.2 1249 2.1.2 (+ 342 patches) local drive detection on Windows error 2.2 1238 wish: darcs help setpref should list all prefs 2.2 1199 Backup files darcs added after external merge 2.2 1043 pull => mergeAfterConflicting failed in geteff (2.0.2+) 2.2 1117 Whatsnew should warn on non-recorded files 2.2 1101 darcs send --cc recipient not included in success message 1287 darcs diff --last: inconsistent behaviour 971 darcs check fails (case sensitivity on filenames) 842 pull => problem gzopening file for write (1.0.9) 1272 amend-record not the same as unrecord + record 1006 darcs check and repair do not look for adds 1109 unwanted progress reports in text editor 946 --extended-usage is shorter than --help! 1196 Asking for changes in /. of directory that doesn't exist gives changes in entire repo 1236 roundup: assigning via email silently fails 1198 Reproducible "mergeConflictingNons failed in geteff with ix" 1097 more up-to-date, editable roundup code 1144 Add darcs send --in-reply-to or --header "In-Reply-To: <[email protected]>" 1189 lock is not deleted on ctrl-C Things remain to be done, not least, perhaps, cutting away additional issues from the bottom, that actually belong to 2.1.2. But prominently, of course, we should finish classifying the undecided issues. I currently see no other way to do this than digging further into the details of each issue. You also ask for the author of the issue resolution: That part is also missing. I am fairly sure that it would need to be attached by hand. Comments, suggestions, and help is most welcome. > ... Best regards Thorkil _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
