From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PHP 5 unstable ?
Date: Sat, 23 Apr 2005 11:07:28 +0200 [thread overview]
Message-ID: <1114247248.13350.35.camel@sponge.fungus> (raw)
In-Reply-To: <426A0E88.3020202@cox.net>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hi,
On Sat, 2005-04-23 at 01:59 -0700, D. Wokan wrote:
> Well then as one of hopefully lots of people, let me chime in with a
> "PHP5 is working for me as well." How is it developers determine if
> something's stable? A lack of bug reports from those of us who added
> entries in our /etc/portage/ files? Where do we report a lack of bugs
> to get these things pushed into the mainstream on Gentoo?
According to bugzilla, there are lots of open bugs (132 to be exact)
containing the word 'php' in the summary. From a quick glimpse many of
them seem related to php-5.
It's Gentoo policy not to mark a package ARCH unless it has been in
portage for 30 days with no open bug reports (not counting enhancement
requests).
If you want to help you can start by going through those bug reports,
coming up with solutions and patches.
Sincerely,
Brix
--
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-23 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 11:57 [gentoo-dev] PHP unstable ? Omer Cohen
2005-04-22 12:12 ` [gentoo-dev] PHP 5 " Omer Cohen
2005-04-22 12:18 ` Stuart Longland
2005-04-22 12:34 ` Francesco Riosa
2005-04-22 12:45 ` Ciaran McCreesh
2005-04-23 8:59 ` D. Wokan
2005-04-23 9:07 ` Henrik Brix Andersen [this message]
2005-04-23 15:27 ` Collins Richey
2005-04-24 4:16 ` D. Wokan
2005-04-22 12:28 ` [gentoo-dev] PHP " Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114247248.13350.35.camel@sponge.fungus \
--to=brix@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox