1. Regular releases
Yes, that would be very nice. But making a release is a lot of work. It has to work on all the platforms supported, not break any test, and there shouldn't be loose ends.
Unfortunally, making a release boils down to a lot of work done by very few people.
2. Moose, Mouse, and autobox.
While I think a better OO system for perl5 would have been wonderful 14 years ago, I don't think perl5 "needs" Moose or Mouse in the core. And they already exist on CPAN. I also don't think changing the OO system this late in the game is worthwhile. Nor do I think it's going to happen. Many people will say "yes". Much bikeshedding will go on. And noone will actually do it.
3. Python's ctypes.
Ah, yes, the old "XS is hard" argument. I can't argue with that. And it would be nice if someone invented something easier, and implemented it. Actually, someone already did, and called in Inline. Again, who's going to do the work?
4. Better CPAN integration.
Easier said then done. There's CPANPLUS and it took a lot of effort to get that integrated in the core. On the author side, there is Module::Build and a few other alternatives to Extutils.
That seems to be an existing Apache module. What's the "need" for perl5?
Nicholas Clark is fond of saying "perl development is driven by people who haven an itch". Which basically means "something is only going to be added/changed if someone is motivated enough to do the work".
Perl5 isn't dead. And Perl5 won't die even if it doesn't implement any of the points mentioned by chromatic. 5.12 will happen. Probably even before perl6.