I don't give you many points for that reasoning. There are always any number of outstanding issues; the amount is only meaningfully limited by a set time frame.
For example, I have in this forum for quite some time ago said that I consider fixing the resolver a prerequisite for a release. Now that's a fair amount of work and I haven't had the inclination to do it. A release can't be held indefinitely because of that, so it's good and well that one is done with a broken resolver anyway. If it were to be done within, say, a month then it could be worth waiting for it, otherwise not. Thus a todo list always have to be set in relation to a suggested deadline.
I'd like to know about a release date at least a week or two in advance. Then I can give you a list of issues I consider embarrassing and/or easy enough to fix before then.
Btw, you contacted me only two days ago about writing a note about sslfile in CHANGES. Maybe you consider two days as an unacceptably long response time so you thought I've just ignored it. I didn't, but I'm unfortunately not always very prompt to answer.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-06 02:22: Subject: Pike 7.6
You are smart enough to understand that when the tree has been forked and the shrinking todo list reaches zero items there will be a release. I have asked _several_ times in this very forum if there were any outstanding issues anyone wanted to fix before release. The issues mentioned has been dealt with (discussed and dismissed or solved).
/ Martin Nilsson (räfsfiskal)