To clarify, I don't think that adding a label that indicates there is code which will probably bitrot and has been asked to address some issue is a bad idea. It's the "closed" problem - GH does not by default automatically search closed issues, and actually I could totally see somebody wanting to add Enigma (or other) pedagogical crypto schemes in the future, who won't know there is pre-existing work.
I'm not sure why it matters if there are 5000 or 10000 open issues, because once there are more than 100 no one can keep track of all of them anyway and you need to search. For better or for worse, there is a big distinction between "fix this Sage notebook bug" which is now truly invalid, and "fix this other bug which has some code but the person couldn't find a job in academia so they don't have time to finish up the small change requested" situation. It's the fact that GH does treat closed tickets differently that means we shouldn't close them (in my opinion). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/e8a75d47-3a5b-4787-8a22-bd775c2c5454n%40googlegroups.com.
