Grokbase Groups PHP pear-qa June 2006
FAQ
Hi all,

I've added a cool add-on for PEAR::PHP_CompatInfo package.
For the best result you'll need at least CVS version or future release 1.0.1

I've a question for QA team. As this package is in stable status and has
no user-docs yet ( i don't count the API docs ), is it possible to
release a new version 1.0.1 without any docs ?

Laurent


-------- Message original --------
Sujet: cvs: pear /PHP_CompatInfo/docs/examples ci_frontend.php
Date: Sat, 10 Jun 2006 17:02:14 -0000
De: farell@php.net ("Laurent Laville")
Pour: pear-cvs@lists.php.net
Forums de discussion: php.pear.cvs

farell Sat Jun 10 17:02:14 2006 UTC

Added files:
/pear/PHP_CompatInfo/docs/examples ci_frontend.php
Log:
A web frontend for PHP_CompatInfo

- requires HTML_QuickForm
- requires HTML_QuickForm_advmultiselect
- PHP_Compat if you run PHP 4 (not necessary with PHP 5)

An easy way to try and check your packages installation
and minimum PHP version requirement

Search Discussions

  • Pierre at Jun 10, 2006 at 9:12 pm

    On Sat, 10 Jun 2006 19:13:12 +0200 pear@laurent-laville.org (Laurent Laville) wrote:

    Hi all,

    I've added a cool add-on for PEAR::PHP_CompatInfo package.
    For the best result you'll need at least CVS version or future
    release 1.0.1

    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    Yes, obviously :)

    -- Pierre
  • Stefano F. Rausch at Jun 11, 2006 at 10:11 am
    Hi ...
    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    I did have the understanding that for stable packages a documentation (as well as regression/unit tests) is a mandatory prerequisite, even if it's only a .txt file. Have things changed in this respect? Have the rules been "relaxed"?

    I'm looking forward to receiving your comments at your earliest convenience.

    Best regards

    -- Stefano

    Pierre wrote:
    On Sat, 10 Jun 2006 19:13:12 +0200
    pear@laurent-laville.org (Laurent Laville) wrote:
    Hi all,

    I've added a cool add-on for PEAR::PHP_CompatInfo package.
    For the best result you'll need at least CVS version or future
    release 1.0.1

    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    Yes, obviously :)

    -- Pierre
  • Pierre at Jun 11, 2006 at 12:02 pm

    On 6/11/06, Stefano F. Rausch wrote:
    Hi ...
    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    I did have the understanding that for stable packages a documentation (as well as regression/unit tests) is a mandatory prerequisite, even if it's only a .txt file. Have things changed in this respect? Have the rules been "relaxed"?
    No, but packages released as stable before the enforcement of these
    rules can obviously still be released.

    In the case of Compatinfo, there is tests, docs and examples in the
    package itself.

    --Pierre
  • Stefano F. Rausch at Jun 11, 2006 at 1:28 pm
    Thanks for the clarification Pierre.


    @ Lukas:
    I wasnt aware of such regulations. AFAIK we just require API documentation and a sort of unwritten rule is some form of end user documentation, where some examples are however considered to be sufficient.
    There are some rules, which are not written down, but are "gentlemen's agreement" within the PEAR community - as you're stating it. My understanding was, that a guide/manual in at least .txt format is more than welcomed.

    So I'm fine with the current situation, I just wanted the status quo to be clarified.

    Thanks again to all.

    -- Stefano

    Pierre wrote:
    On 6/11/06, Stefano F. Rausch wrote:
    Hi ...
    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    I did have the understanding that for stable packages a documentation
    (as well as regression/unit tests) is a mandatory prerequisite, even
    if it's only a .txt file. Have things changed in this respect? Have
    the rules been "relaxed"?
    No, but packages released as stable before the enforcement of these
    rules can obviously still be released.

    In the case of Compatinfo, there is tests, docs and examples in the
    package itself.

    --Pierre
  • Lukas Smith at Jun 11, 2006 at 12:36 pm

    Stefano F. Rausch wrote:
    Hi ...
    I've a question for QA team. As this package is in stable status and
    has no user-docs yet ( i don't count the API docs ), is it possible
    to release a new version 1.0.1 without any docs ?
    I did have the understanding that for stable packages a documentation
    (as well as regression/unit tests) is a mandatory prerequisite, even if
    it's only a .txt file. Have things changed in this respect? Have the
    rules been "relaxed"?
    I wasnt aware of such regulations. AFAIK we just require API
    documentation and a sort of unwritten rule is some form of end user
    documentation, where some examples are however considered to be sufficient.

    regards,
    Lukas

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-qa @
categoriesphp
postedJun 10, '06 at 5:13p
activeJun 11, '06 at 1:28p
posts6
users4
websitepear.php.net

People

Translate

site design / logo © 2021 Grokbase