where did phpunit go?

Hello,

this question is fairly frequent in #pear.
i think we need to figure out a cleaner way for situations
like this ..
i think the package homepage should be revived. we should
put a note on 
there.

as for installing .. do we still have the releases? if so
they should 
atleast we listed on the package homepage, so that people
can install by 
url. i guess all of this requires some special hackery into
pearweb. but 
the current situation is bad. until the necessary hacks are
done i would 
prefer if phpunit would be come just like any package again,
with the 
note on the homepage.

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Sebastian Bergmann wrote:
> Lukas Kahwe Smith wrote:
>> i think the package homepage should be revived
> 
>  Please don't. Or only if people cannot report bugs. I
had the project
>  deleted because people were still filing bugs on
pear.php.net instead of
>  www.phpunit.de.

So if we look at the requirements for this to work cleanly,
working from 
the status quo that PHPUnit is restored as a full package in
PEAR again:

- note on the package homepage on pear.php.net
- disable bug tracker
- disable pear install PHPUnitx

what else?

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Sebastian Bergmann wrote:
> Lukas Kahwe Smith wrote:
>> So if we look at the requirements for this to work
cleanly, working 
>> from the status quo that PHPUnit is restored as a
full package in 
>> PEAR again:
> 
>  Please note that I have no interest in "restoring
PHPUnit as a full
>  package in PEAR" again. This duplication is
contraproductive in the
>  long run, IMHO. PHPUnit has nothing to do with PEAR
anymore. Period.
> 
>  Besides, http://pear.php.n
et/package/PHPUnit and
>  http://pear.php.
net/package/PHPUnit2 redirect to www.phpunit.de so I
>  find it hard to understand why people have problems
finding out about
>  PHPUnit's move.

My point is that PEAR has always taken the stance that it
will offer any 
code ever made available via pear.php.net until eternity. We
do not know 
what will happen with phpunit.de, so we need to take steps
to retain 
this commitment on our side.

The fact is that many people stumble over this. Now we can
have them 
stumble over getting their old code, documented install
procedures etc 
to work, or we can have them stumble when it comes time to
upgrade to 
the latest shiny new version of PHPUnit. I rather have them
stumble on 
that last point than on the first.

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Sebastian Bergmann wrote:
> Lukas Kahwe Smith wrote:
>> So if we look at the requirements for this to work
cleanly, working 
>> from the status quo that PHPUnit is restored as a
full package in 
>> PEAR again:
> 
>  Please note that I have no interest in "restoring
PHPUnit as a full
>  package in PEAR" again. This duplication is
contraproductive in the
>  long run, IMHO. PHPUnit has nothing to do with PEAR
anymore. Period.
> 
>  Besides, http://pear.php.n
et/package/PHPUnit and
>  http://pear.php.
net/package/PHPUnit2 redirect to www.phpunit.de so I
>  find it hard to understand why people have problems
finding out about
>  PHPUnit's move.

Hi Sebastian,

People have trouble because nobody bothers to type
"package" and
http://pear.php.net/phpun
it is a 404.  Also, when searching PEAR for
PHPUnit there is no evidence that the package ever existed
or
instructions on where to find it.

I understand you are frustrated with the way PEAR has worked
for you,
but it reflects badly on both you and PEAR to completely
remove the
previous work.  I'd like to re-add the PHPUnit package and
have the
"Bugs" tab redirect to your trac.  Please advise
on this solution.

I recently added the ability to deprecate a package to
another channel,
specifically for PHPUnit, and was surprised to see it was
gone, could
you describe how the decision was made on what to do with
phpunit, and
who implemented it at pear.php.net?

Thanks,
Greg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On Tue Feb 20, 2007 at 09:4344PM -0600, Gregory Beaver
wrote:
> I recently added the ability to deprecate a package to
another channel,
> specifically for PHPUnit, and was surprised to see it
was gone, could
> you describe how the decision was made on what to do
with phpunit, and
> who implemented it at pear.php.net?

I deleted the package on Sebastian's request and suggested
to set up a
rewrite rule to at least point people to PHPUnit's new home.
 I must
admit that I did not expect this to be such a problem for
people ...

- Martin

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Sebastian Bergmann wrote:
> Lukas Kahwe Smith wrote:
>> We do not know what will happen with phpunit.de
> 
>  Nor should you care as PHPUnit is no longer a PEAR
project.

Of course we still care .. PEAR is commited to all code that
ever was 
released through pear.php.net .. until eternity.

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

What is wrong with the "New package (superseding this
one):" feature
of pearweb? you could create dummy packages that refer to
the "new"
place ... and they should still be searchable etc via
pear.php.net, or
do i misunderstand the purpose of this feature?

Regards,
Stefan

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Stefan Walk wrote:
> What is wrong with the "New package (superseding
this one):" feature
> of pearweb? you could create dummy packages that refer
to the "new"
> place ... and they should still be searchable etc via
pear.php.net, or
> do i misunderstand the purpose of this feature?

Hi,

As Sebastian doesn't care about any previous users of
PHPUnit at
pear.php.net, all we need to do is ignore him and take care
of our own here.

I would like to add PHPUnit and PHPUnit2 back, release the
last version
of PHPunit/2 based on CVS at pear, revert the redirects for
pear.php.net/package/PHPUnit and instead redirect to
phpunit.de for the
"Bugs" tab.

Without any jab at Martin, this highlights the need for a
more
transparent decision-making process.  Obviously, one person
acting with
the best intentions cannot account for all contingencies,
and it puts an
unfair burden on that person when things go wrong.  I will
try to get
the referendum for a new PEAR governing structure election
text ready so
the election can begin soon. (i.e. within a month).

Thanks,
Greg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Just add the package home page with a BIG message to
indicate the move. 
That is really all we need.

Arnaud.

Gregory Beaver wrote:
> Stefan Walk wrote:
>> What is wrong with the "New package
(superseding this one):" feature
>> of pearweb? you could create dummy packages that
refer to the "new"
>> place ... and they should still be searchable etc
via pear.php.net, or
>> do i misunderstand the purpose of this feature?
> 
> Hi,
> 
> As Sebastian doesn't care about any previous users of
PHPUnit at
> pear.php.net, all we need to do is ignore him and take
care of our own here.
> 
> I would like to add PHPUnit and PHPUnit2 back, release
the last version
> of PHPunit/2 based on CVS at pear, revert the redirects
for
> pear.php.net/package/PHPUnit and instead redirect to
phpunit.de for the
> "Bugs" tab.
> 
> Without any jab at Martin, this highlights the need for
a more
> transparent decision-making process.  Obviously, one
person acting with
> the best intentions cannot account for all
contingencies, and it puts an
> unfair burden on that person when things go wrong.  I
will try to get
> the referendum for a new PEAR governing structure
election text ready so
> the election can begin soon. (i.e. within a month).
> 
> Thanks,
> Greg
> 

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Le 21 févr. 07 à 15:47, Arnaud Limbourg a écrit :

> Just add the package home page with a BIG message to
indicate the  
> move. That is really all we need.

You don't build a dynamic website of this size with patches
applied  
here and there. It is better to get rid of the exception,
unless it  
becomes the rule. That's just my opinion.


--
Bertrand Mansion
Mamasam
Work : http://www.mamasam.com
Blog : http://golgote.freeflux.n
et

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php