Changes between Version 1 and Version 2 of SeaChange/DevelopmentProcess

Timestamp:

Oct 12, 2014, 3:00:59 AM (10 years ago)

Author:

anonymous

Comment:

—

SeaChange/DevelopmentProcess

@@ -11 +11 @@
  5. Historically, there's effectively zero chance of a plugin getting into the core.   
  6. Features that users think should be "core" are not (''this is '''very''' subjective'').
+ 7. Many Trac tickets age in a limbo of sorts when they could probably be closed.
 
 
@@ -85 +86 @@
     ''strictly necessary for almost anyone using Trac (`trac.`)'' and
     ''optional, must be 3rd party.''
+
+=== 7. Many Trac tickets age in a limbo of sorts when they could probably be closed.
+    The 1000+ active tickets, often old and with inflated severity, give a false impression of the project. See for instance the history of scary #11174 'blocker', an InstallationIssue that should probably be closed as invalid. Some very old tickets relevant to points 3. and 6. above could be closed as 'wontfix', perhaps with a note suggesting interested parties could write a patch and reopen the ticket if it is still relevant. Many other could be set to low priority and moved to the 'unscheduled' milestone to help reduce the clutter.