who lead perl5 develop?
Noone in particular. There are a handful of a developers who do most of the work, and hence, by just doing the work, "lead" perl 5 development. And there's a pumpking, who may make decisions if decisions have to be made, and no consensus can be reached. He also will be the main person deciding what are "blockers" for a next release (but not the only one), and he's the person who keeps in touch with the release manager of the month. But the last the pumpkings aren't C programmers, and hence don't add much core features (nor solve bugs).
who determine if add X Y feature into perl5?
Mostly by the person actually implementing feature X Y. That's were it starts. If noone actually implements X Y, it does not get added. A feature may not be added if the p5p mailing list decides it either 1) breaks existing syntax, 2) is inefficient, 3) can be done with a CPAN module instead, 4) add too little value to compensate for the added complexity in the internals, 5) has the potential to be confusing, 6) is poorly designed, 7) some other reason. But noone is saying "this is what will be implemented".
But next month, perl 5.16 will be released, and as this 5.12 won't be supported soon. Does I need to upgrade my perl I installed even though new perl doesn't bring exciting features?
No. It just means it's unlikely that someone will release 5.12.5. 5.12.4 will not stop working. Now, it may be that 15 years from now, 5.12.4 no longer compiles out of the box, because you've upgraded your OS 17 times, and your C compiler is 5 major version further, but it seems unlikely you would upgrade your Perl in those cases. Now, just because it's unlikely 5.12.5 will be released, if someone is willing to do the work, some years from now, we may have a 5.12.17. And a 5.8.33. And perhaps a 1.0.22. But considering the people that actually do significant core work is very, very low, and they have shown no interest in maintaining 5.12 next to 5.16 and 5.14, I don't think 5.12.5 will happen.
But again, a release of 5.16 does not mean people will come over to you in the middle of the night, demanding you to delete your 5.12 from your system.
But next month, perl 5.16 will be released, and as this 5.12 won't be supported soon. Does I need to upgrade my perl I installed even though new perl doesn't bring exciting features?
Which modules are included in the core isn't determined by vote. For a module to be included in the core, there has to be a good reason ("needed for the build process" is a good reason; "needed to bootstrap fetching and building from CPAN" is a good reason; "tightly tied to the core" (as in, will need a rewrite if the perl internals get reshuffled) is a good reason; and that's about it for good reasons).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
