Changes between Version 272 and Version 273 of SprintIdeas

Timestamp:

Apr 28, 2012, 7:24:29 AM (12 years ago)

Author:

Ramiro Morales

Comment:

remove spam

SprintIdeas

@@ -68 +68 @@
  * Find bugs that have been confirmed and explained, but haven't got a programatic test case. Every bug that is fixed in Django should be accompanied by a regression test to make sure the problem doesn't arise again. Once a test case exists, it's much easier for someone who understands the internals to fix the problem.
  * Look for tickets [http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&needs_docs=1&order=priority&stage=Accepted needing documentation] or needing improved documentation and try to complete them.
- * Verify that old bugs still exist. Sometimes bugs get inadvertantly fixed; either they're re-reported but not identified as duplicates, or a fix for one bug corrects another bug. These old tickets will continue to linger in the bug tracker unless someone confirms that they are no longer a problem. [http://www.articlesbase.com/criminal-articles/inteligator-review-3700882.html inteligator review]
+ * Verify that old bugs still exist. Sometimes bugs get inadvertantly fixed; either they're re-reported but not identified as duplicates, or a fix for one bug corrects another bug. These old tickets will continue to linger in the bug tracker unless someone confirms that they are no longer a problem.
 
 == Suggestions ==