Re: Packages sticky messages : not maintained - and Net_Growl News (roadmap)

From: Date: Sun, 26 Jul 2009 08:51:53 +0000
Subject: Re: Packages sticky messages : not maintained - and Net_Growl News (roadmap)
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-52488@lists.php.net to get a copy of this message
Just my feeling about such operation. If there are so many package in XML 1.0, that means probably that authors do not read anymore the pear-dev mailing list. PEAR Group should use an alternate solution. Contact first all author by mail. And if they don't respond in an acceptable time limit (1 month) than consider them as inactive and PEAR-QA team may do what they want. That will avoid such surprise ! Just additionnal info about Net_Growl : I will not be the new leader (Bertrand is the right guy) and even less active. Rather consider me as a contributor I'll just give available on my web site 3 versions as detailed previously. In case of Bertrand decide to not maintain anymore the package, PEAR-QA / Group will do what they want. Either : - Add 0.8.0b1 (package xml 2.0 migration and coding standard fixes) in PEAR repository - Add 0.9.0b1 - Add 2.0.0b1 I'll keep maintain it on my own website, because I love Growl Notification System . Daniel O'Connor a écrit :
That was probably me, also. It's on the list of stuff at http://wiki.php.net/pear/packages/migration ; and there's been a few mailing list posts about this: http://news.php.net/php.pear.qa/5129 http://www.nabble.com/Please-update-package.xml-to-version-2-by-September-1st,-2008-td18554971.html I went through, and if it was on the first list; and still displaying: *WARNING: the last release of this package used package.xml version 1.0*, which is deprecated. To use package.xml version 2.0, run "pear convert" to create package2.xml. Both package.xml and package2.xml may be used together, or you may choose to replace package.xml with package2.xml for the next release. It got marked as unmaintained because of that. Feel free to unmark it. On Sun, Jul 26, 2009 at 5:47 PM, Laurent Laville <pear@laurent-laville.org <mailto:pear@laurent-laville.org>> wrote:
    Hello,
    I would like to know who decided to add the sticky message below
    other than the package leader ?
    "This package is not maintained, if you would like to take over
    please go to this page."
    While I marked myself [1] as inactive on all my package, I've not
    decided to put Services_W3C_CSSValidator unmaintained.
    And what a suprise to see Daniel O'Connor to ask me about a new
    release in such condition !
    Other case, I'm suprised to see today, while I visit page of
    PEAR::Net_Growl. Again the same unmaintained sticky message.
    Who put it ?
    Everybody should know, that I work since few days now with
    Bertrand Mansion, author of Net_Growl (and package leader) to
    produce and give available new versions very soon (probably in 3
    days).
    Versions ready:
    * Net_Growl 0.8.0b1 - is a cosmetic release to follow current PEAR
    stantard
    Versions awaiting:
    * Net_Growl 0.9.0b1 - is a release that support both old protocol
    UDP and new protocol GNTP [2]. This version is still backward
    compatible with 0.7.0 and PHP4
    * Net_Growl 2.0.0b1 - is a release with same features as Net_Growl
    0.9.0b1 but was rewrote in PHP5 (no dependency: even with PEAR core).
    "Know what happens" should be the end words.
    [1] http://pear.php.net/user/farell
    [2] http://www.growlforwindows.com/gfw/help/gntp.aspx
    --     PEAR Development Mailing List (http://pear.php.net/)
    To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.pear.dev (#52488) next »