On Thursday, January 2, 2003, at 05:08 AM, John Coggeshall wrote:
When it comes to bug reporting/fixing, perhaps it's feasible to
completely separate bug reporting for each module from PHP itself? For
example, if each module is maintained completely separately from PHP
with it's own version # th
> [John Coggeshall]
> These are all just thoughts I have.. Feedback is more than welcome. I
> think a system such as this would accomplish a number of (in my mind)
> benfitial things:
>
> 1) Faster and easier installations of PHP
> [...]
>
> 2) More accurate and managable module maintaing
> [...]
lto:[EMAIL PROTECTED]]
>Sent: Thursday, January 02, 2003 3:59 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)
>
>
>> [...]
>> different distribution packages can be
>> built when php releases occure, such as &
> [...]
> different distribution packages can be
> built when php releases occure, such as 'php core' which would contain
> the 'most important' stable extensions, 'php stable' which would contain
> all stable extensions, and 'php bleeding' which could be a package with
> the latest development s
> >> I think this would make
> >> releasing new versions of php much more manageable.
> >
> > Do you? Not every extension has a named maintainer ..
>
> At worst, the maintenance would be as it is now. Or is the worry that
> some extensions will go unmaintained if they are moved into PECL? My
>
I think this would make
releasing new versions of php much more manageable.
Do you? Not every extension has a named maintainer ..
At worst, the maintenance would be as it is now. Or is the worry that
some extensions will go unmaintained if they are moved into PECL? My
take on that would
> With this also extensions now can take on a life of their own,
releasing
> at different times than php, and visaverse. I think this would make
> releasing new versions of php much more manageable.
Do you? Not every extension has a named maintainer ..
>
> Shane
>
- Steph
--
PHP Development
Roadmap:
1. Switch to ZE2 by default
2. Establish PECL CA authority and binary package/release process
(particularly important for win32)
3. Bundle PHP-Soap (and stop the "bleeding of PHP users")
3a. Collect underpants
4. ?
5. Profit
#3 doesn't belong in a general roadmap. What does
> 3. Bundle PHP-Soap (and stop the "bleeding of PHP users")
I know I've been saying for a while now that I'm going to start working on
this again but I have yet to do it. I do plan to work on this again. I would
like to see it bundled with php5 but it defintly needs some work. If its
possible I
I hope you all had a joyous night last night and that it forms that
start of a great New Year!
Now, let's get our heads straight on what we are doing for 2003 :)
You may remember (especially if you read Derick's Look Back) that I said
something about building against ZE2 by default once we releas
10 matches
Mail list logo
