Article Publishing scheduling is already there. Use the Dates feature while you add articles. CRON is NOT the answer.
Attachments really work so not sure what you meant by the same?
News by email: Do you think a shared host with a limit of 200 mails/hr will ever work? All shared hosting accounts impose the limits on mails/hr. How many PHPCow sites are hosted on Dedicated server? This would open up huge dissatisfaction levels as host will simply say -- Oh script is resource intensive -- and then PHPCow will have a huge list of people hurling the same statement to them and then not be ready to accept the TRUTH that for this a Dedicated server is needed. Imagine a PHPCow site with 1000 users having done News By Email. What happens to server everytime you add a news? Doing thru cron could make it eve worse .... 1000 users 20 news item added == 20,000 mails going unless it's made out to be a digest which also would mean 1000 mail/site. Shared host would be quick to suspend the account for sure.
Publish/Unpublish is there. You can Hide articles even after publishing. Rest is possible depending upon how you play with your blocks.
User Prefix with date: Use the Date function : Prefix to get what you want.
Support: I guess the major area where PHPCow needs to think is starting PAID commercial support like many vendors (Including big guns like Oracle, bitrix and others) do. Offer PAID support on per instance basis.
Hi:
Well, I only mentioned TinyMCE as an example, making a comparison between the current phpcow wysiwyg editor and a more feature rich editor.. This said, I just want a better editor, call it TinyMCE, FCKeditor, or another one.
When I publish an article with a future date, the article will appear on public view on that date.. that's for sure.. but, have you noticed that even when the article is set up to appear on a future date, it does appear on RSS feed right away and not on the future date/time you have set? I know cron is not the solution but an option that could be implemented.
Btw, setting up a Cron is not exclusive to dedicated servers and you can even use an external cron service (there are free ones) if you don't have access to SSH or a Cpanel cron.
Attachments... well, I dont know if it's only me, but in case of file attachments, I just don't know what is the point of the Attachment title & attachment description if none of them are "attached" to the file when posting it to the template.
Image attachments are ok.
News by email: I agree with you when you say that shared hosting has limits on number of emails sent per hour, but as you say, this depends on host configuration. A workaround on this is to use an external service, like Feedburner, that provides daily email subscriptions.
Prefix: yes, you can use the article.prefix along with article.date function on the article template, but I would like to use both date and prefix on category block, so when I'm creating ie, a single block I can choose to use date and predefined prefix both at a time.. Can you do that?
Support: You are going to excuse me here, but I don't agree with you at this point, first of all because Phpcow is not a platform or a mission critical software like Oracle. And second, because we are paying for the software. I really don't imagine asking a simple support question like "Can I do x stuff with phpcow?", then I pay "15usd per incident" and they answer "No, it's not possible at this time". Great.
More simple: can you imagine paying Microsoft for all the patches and security fixes they release for XP or Vista every month? 
I have been with my hosting company for 7 years, and I don't plan to move at this time. I have been using Phpcow for almost a year, and the most "serious" incident I have had was caused by the php soap thing. Phpcow released a fix and that was it.
And because Phpcow is not a "one size fits all", there are some minor issues that are not solved yet. The cause? maybe my server configuration, maybe a bug in phpcow.. how to be sure? who knows. So phpcow should take note on the configs used by their clients to improve the software and at the same time improve the support given to clients.
So, for me, paid-only support is not an option right now. Many clients will migrate from phpcow to other software options. 
And finally, as the topic states, these are "features you would like to see" and everyone is invited to post the features they want to see. This is not an official phpcow forum, so maybe there is no need for a rude discussion 
Regards
