diff options
author | Thomas Schwinge <tschwinge@gnu.org> | 2009-10-17 14:43:11 +0200 |
---|---|---|
committer | Thomas Schwinge <tschwinge@gnu.org> | 2009-10-17 14:49:07 +0200 |
commit | 31633c7addf25619a2a3042fc3e27f21aa97a831 (patch) | |
tree | 1bca093c7f177d35ee0cd68a81a7ed5ab5ec5e69 /doc/forum/ever-growing_list_of_pages.mdwn | |
parent | 69a1ebce16debf8b0aeb61329ff26d235e248e7d (diff) |
Add some more reasoning. Split out unrelated issue.
Diffstat (limited to 'doc/forum/ever-growing_list_of_pages.mdwn')
-rw-r--r-- | doc/forum/ever-growing_list_of_pages.mdwn | 19 |
1 files changed, 13 insertions, 6 deletions
diff --git a/doc/forum/ever-growing_list_of_pages.mdwn b/doc/forum/ever-growing_list_of_pages.mdwn index 435b12c8c..9920e34bb 100644 --- a/doc/forum/ever-growing_list_of_pages.mdwn +++ b/doc/forum/ever-growing_list_of_pages.mdwn @@ -5,10 +5,6 @@ they're still present in the repository. Shouldn't there be some clean-up at some point for those that have been resolved? Or should all of them be kept online forever? -Likewise, for example in [[forum/ikiwiki__39__s_notion_of_time]], should one -remove the text about the implementation bug that has been fixed, or should it -stay there, for reference? - --[[tschwinge]] > To answer a question with a question, what harm does having the done bugs @@ -18,5 +14,16 @@ stay there, for reference? > running older versions of the Ikiwiki software may find the page explaining > that the bug is fixed if they perform a search. -- [[Jon]] -> I like to keep old bugs around. OTOH, I have no problem with cleaning up -> obsolete stuff in the forum, tips, etc. --[[Joey]] +> I like to keep old bugs around. --[[Joey]] + +So, I guess it depends on whether you want to represent the development of the +software (meaning: which bugs are open, which are fixed) *(a)* in a snapshot of +the repository (a checkout; that is, what you see rendered on +<http://ikiwiki.info/>), or *(b)* if that information is to be contained in the +backing repository's revision history only. Both approaches are valid. For +people used to using Git for accessing a project's history, *(b)* is what +they're used to, but for those poor souls ;-) that only use a web browser to +access this database, *(a)* is the more useful approach indeed. For me, using +Git, it is a bit of a hindrance, as, when doing a full-text search for a +keyword on a checkout, I'd frequently hit pages that reported a bug, but are +tagged `done` by now. --[[tschwinge]] |