[PEPr] +1 for RFC::VersionNaming
| From: | Laurent Laville | Date: | Mon, 22 Nov 2004 13:00:02 +0000 |
| Subject: | [PEPr] +1 for RFC::VersionNaming | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34487@lists.php.net to get a copy of this message | ||
Laurent Laville (http://pear.php.net/user/farell) has voted +1 on the proposal for
RFC::VersionNaming.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=65
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=65&handle=farell
This vote is conditional. The condition is:
I like it; it's enough clear only for point below :
You wrote :
"- General discussion on pear-group indicated that no complete agreement could
be reached on the 2 controversial points (RC/package state suffixes.), as a
result, the conclusion is that they should be proposed as seperate RFC's."
Does it means we have to vote without this particular but essential note (in my point of view: due
to current conflit with case html_css) ?
And should it be a limit in state suffix naming ?
For example:
x.y.zRCn with n = 1,2,3 what is the max ?
x.y.zbetan with n = 1,2,3, what is the max ?
Sorry if i've missed an important thread before !
--
Sent by PEPr, the automatic proposal system at http://pear.php.net