Home > Archive > PHP PEAR Questions and Answers > July 2007 > About PEAR_Info ... and RC3
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
About PEAR_Info ... and RC3
|
|
| Laurent Laville 2007-07-09, 7:00 pm |
| Hi QA Team,
I've in mind to release another version (Release Candidate 3) with some
changes since RC2, before final stable 1.7.0 scheduled for July 17.
Here are what I thought.
Split current PEAR_Info class with general information (packages,
channels, config) and PEAR credits in another class PEAR_Credits.
Something like PHP's phpinfo() and phpcredits()
Are you agree, following PEAR standards, to have a PEAR_Info package
with two classes PEAR_Info and PEAR_Credits inside ?
Waiting for comment
Regards
Laurent Laville
| |
| Laurent Laville 2007-07-09, 7:00 pm |
| Laurent Laville a écrit :
> Hi QA Team,
>
> I've in mind to release another version (Release Candidate 3) with some
> changes since RC2, before final stable 1.7.0 scheduled for July 17.
>
> Here are what I thought.
> Split current PEAR_Info class with general information (packages,
> channels, config) and PEAR credits in another class PEAR_Credits.
>
> Something like PHP's phpinfo() and phpcredits()
>
> Are you agree, following PEAR standards, to have a PEAR_Info package
> with two classes PEAR_Info and PEAR_Credits inside ?
>
> Waiting for comment
>
> Regards
> Laurent Laville
Forgot to ask, if someone could give me an exhaustive names list of :
- PEAR Group
- PEAR Documentation Team
- PEAR Website Team
- PEAR QA
because I want to avoid names hard coded into php code, and externalize
these lists for future releases.
| |
| Laurent Laville 2007-07-09, 7:00 pm |
| Laurent Laville a écrit :
> Hi QA Team,
>
> I've in mind to release another version (Release Candidate 3) with some
> changes since RC2, before final stable 1.7.0 scheduled for July 17.
>
> Here are what I thought.
> Split current PEAR_Info class with general information (packages,
> channels, config) and PEAR credits in another class PEAR_Credits.
>
> Something like PHP's phpinfo() and phpcredits()
>
> Are you agree, following PEAR standards, to have a PEAR_Info package
> with two classes PEAR_Info and PEAR_Credits inside ?
>
> Waiting for comment
>
> Regards
> Laurent Laville
Forget what I've said. No need to split informations into two classes,
but the behavior to have a such phpcredits() function will remain for
future RC3.
|
|
|
|
|