Services_Technorati2

I'd like to deprecate my original Services_Technorati
package (which  
has yet to reach a stable release because of some
dependencies) and  
replace it with a new PHP5-only package, but had a few
questions. If  
these are answered somewhere in the manual that I've missed,
please  
point me there.

How do I get CVS and the package homepage set up for the new
version?  
I'm guessing I email pear-group?

How should I number the beta releases? I see that MDB2 just
used  
2.0.0betaX and I'd be happy to go down that route, but
wanted to  
maintain consistency with any accepted approach.

thanks. James.

-- 
James Stewart

Play: http://james.ant
hropiccollective.org
Work: http://jystewart.net/pr
ocess/

James,


> I'd like to deprecate my original Services_Technorati
package (which  
> has yet to reach a stable release because of some
dependencies) and  
> replace it with a new PHP5-only package, but had a few
questions. If  
> these are answered somewhere in the manual that I've
missed, please  
> point me there.
> 
> How do I get CVS and the package homepage set up for
the new version?  
> I'm guessing I email pear-group?
Just release a new version. There is no need to switch CVS
directories; you can tag the old version (cvs tag ...) so
that people can still get the old code.
Then remove the files from CVS and start fresh.


Christian

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

On Feb 20, 2007, at 11:42 AM, Christian Weiske wrote:
>> I'd like to deprecate my original
Services_Technorati package (which
>> has yet to reach a stable release because of some
dependencies) and
>> replace it with a new PHP5-only package, but had a
few questions. If
>> these are answered somewhere in the manual that
I've missed, please
>> point me there.
>>
>> How do I get CVS and the package homepage set up
for the new version?
>> I'm guessing I email pear-group?
>
> Just release a new version. There is no need to switch
CVS  
> directories; you can tag the old version (cvs tag ...)
so that  
> people can still get the old code.
> Then remove the files from CVS and start fresh.

Thanks. I've done that and it seems to be working well.

But when I try to package a new release, with the name
change to  
Services_Technorati2 and upload it to PEAR the site gives me
the error:

     * Package name in package.xml
"Services_Technorati2" MUST match  
exactly package name on the website ""

James.


-- 
James Stewart
Play: http://james.ant
hropiccollective.org
Work: http://jystewart.net/pr
ocess/

Arriving late.

The way it is handled usually is the creation of a new
package, not 
reuse of the previous one.

A php4 package upgraded to PHP5 would break on upgrade so we
create a 
new package.

Arnaud.

James Stewart wrote:
> On Feb 20, 2007, at 11:42 AM, Christian Weiske wrote:
>>> I'd like to deprecate my original
Services_Technorati package (which
>>> has yet to reach a stable release because of
some dependencies) and
>>> replace it with a new PHP5-only package, but
had a few questions. If
>>> these are answered somewhere in the manual that
I've missed, please
>>> point me there.
>>>
>>> How do I get CVS and the package homepage set
up for the new version?
>>> I'm guessing I email pear-group?
>>
>> Just release a new version. There is no need to
switch CVS 
>> directories; you can tag the old version (cvs tag
...) so that people 
>> can still get the old code.
>> Then remove the files from CVS and start fresh.
> 
> Thanks. I've done that and it seems to be working
well.
> 
> But when I try to package a new release, with the name
change to 
> Services_Technorati2 and upload it to PEAR the site
gives me the error:
> 
>     * Package name in package.xml
"Services_Technorati2" MUST match 
> exactly package name on the website ""
> 
> James.
> 
> 
> --James Stewart
> Play: http://james.ant
hropiccollective.org
> Work: http://jystewart.net/pr
ocess/
> 
> 
> 
> 

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

Arnaud Limbourg wrote:
> Arriving late.
> 
> The way it is handled usually is the creation of a new
package, not
> reuse of the previous one.
> 
> A php4 package upgraded to PHP5 would break on upgrade
so we create a
> new package.

Hi,

Actually, this is not a BC break for one simple reason: the
pear
installer will not allow you to upgrade to a package version
that does
not work in your php version.

Also, because Services_Technorati never reached 1.0.0 or
stable, I don't
see this as a huge deal.

However, you should be prepared, James, should there be any
security-related bugs, to release 0.6.7 beta with PHP4
support and the
fix.  Hopefully this will never need to happen, but please
don't plan
for a perfect future, that rarely makes life easier should
anything go
wrong .

Thanks,
Greg

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

On Feb 21, 2007, at 9:47 AM, Gregory Beaver wrote:
> Arnaud Limbourg wrote:
>> Arriving late.
>>
>> The way it is handled usually is the creation of a
new package, not
>> reuse of the previous one.
>>
>> A php4 package upgraded to PHP5 would break on
upgrade so we create a
>> new package.
>
> Hi,
>
> Actually, this is not a BC break for one simple reason:
the pear
> installer will not allow you to upgrade to a package
version that does
> not work in your php version.

Okay. I'm quite happy to go with the consensus on this. But
if  
someone could send me an example of what the version tag in
my  
package.xml (v2) file should look like for 2.0.0alpha1
that'd be great!

> Also, because Services_Technorati never reached 1.0.0
or stable, I  
> don't
> see this as a huge deal.
>
> However, you should be prepared, James, should there be
any
> security-related bugs, to release 0.6.7 beta with PHP4
support and the
> fix.  Hopefully this will never need to happen, but
please don't plan
> for a perfect future, that rarely makes life easier
should anything go
> wrong .

Yeah, I'll just hope for a perfect future but keep an eye on
bug  
reports for any version.

thanks. James.


-- 
James Stewart
Play: http://james.ant
hropiccollective.org
Work: http://jystewart.net/pr
ocess/

On Feb 21, 2007, at 9:32 AM, James Stewart wrote:
> On Feb 20, 2007, at 11:42 AM, Christian Weiske wrote:
>>> I'd like to deprecate my original
Services_Technorati package (which
>>> has yet to reach a stable release because of
some dependencies) and
>>> replace it with a new PHP5-only package, but
had a few questions. If
>>> these are answered somewhere in the manual that
I've missed, please
>>> point me there.
>>>
>>> How do I get CVS and the package homepage set
up for the new  
>>> version?
>>> I'm guessing I email pear-group?
>>
>> Just release a new version. There is no need to
switch CVS  
>> directories; you can tag the old version (cvs tag
...) so that  
>> people can still get the old code.
>> Then remove the files from CVS and start fresh.
>
> Thanks. I've done that and it seems to be working
well.
>
> But when I try to package a new release, with the name
change to  
> Services_Technorati2 and upload it to PEAR the site
gives me the  
> error:
>
>     * Package name in package.xml
"Services_Technorati2" MUST match  
> exactly package name on the website ""

Did anyone have any further thoughts on this? I'm still
getting this  
error when I try to install my package. Should I file a
bug?

James.


-- 
James Stewart
Play: http://james.ant
hropiccollective.org
Work: http://jystewart.net/pr
ocess/

James Stewart wrote:
> On Feb 21, 2007, at 9:32 AM, James Stewart wrote:
>> On Feb 20, 2007, at 11:42 AM, Christian Weiske
wrote:
>>>> I'd like to deprecate my original
Services_Technorati package (which
>>>> has yet to reach a stable release because
of some dependencies) and
>>>> replace it with a new PHP5-only package,
but had a few questions. If
>>>> these are answered somewhere in the manual
that I've missed, please
>>>> point me there.
>>>>
>>>> How do I get CVS and the package homepage
set up for the new version?
>>>> I'm guessing I email pear-group?
>>>
>>> Just release a new version. There is no need to
switch CVS
>>> directories; you can tag the old version (cvs
tag ...) so that people
>>> can still get the old code.
>>> Then remove the files from CVS and start
fresh.
>>
>> Thanks. I've done that and it seems to be working
well.
>>
>> But when I try to package a new release, with the
name change to
>> Services_Technorati2 and upload it to PEAR the site
gives me the error:
>>
>>     * Package name in package.xml
"Services_Technorati2" MUST match
>> exactly package name on the website ""
> 
> Did anyone have any further thoughts on this? I'm still
getting this
> error when I try to install my package. Should I file a
bug?

Hi James,

Take a look at PEAR_PackageFileManager.  What I did was
release with a
new class, PEAR_PackageFileManager2 inside the existing
package.  You
must keep the same package name, or release it as a new
package.  This
is one way we keep from confusing users.

I haven't yet had time to investigate this email thread
fully, but I
will try to later today.

Thanks,
Greg

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

James Stewart wrote:
> On Feb 20, 2007, at 11:42 AM, Christian Weiske wrote:
>>> I'd like to deprecate my original
Services_Technorati package (which
>>> has yet to reach a stable release because of
some dependencies) and
>>> replace it with a new PHP5-only package, but
had a few questions. If
>>> these are answered somewhere in the manual that
I've missed, please
>>> point me there.
>>>
>>> How do I get CVS and the package homepage set
up for the new version?
>>> I'm guessing I email pear-group?
>>
>> Just release a new version. There is no need to
switch CVS
>> directories; you can tag the old version (cvs tag
...) so that people
>> can still get the old code.
>> Then remove the files from CVS and start fresh.
> 
> Thanks. I've done that and it seems to be working
well.
> 
> But when I try to package a new release, with the name
change to
> Services_Technorati2 and upload it to PEAR the site
gives me the error:
> 
>     * Package name in package.xml
"Services_Technorati2" MUST match
> exactly package name on the website ""

Hi James,

Having investigated more closely, Christian was not
suggesting that you
change the package name, only that you re-do the code.

To be really explicit, name the thing
"Services_Technorati" and name the
class "Services_Technorati" .  The
PHP_Parser package is an example of
this kind of switch.  The first release 0.1 was
php4-compatible.  The
upcoming release makes use of PHP_ParserGenerator and is
therefore
PHP5+.  I didn't change the name of the package or class,
just the contents.

Greg

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

On Feb 23, 2007, at 10:32 AM, Greg Beaver wrote:
> Having investigated more closely, Christian was not
suggesting that  
> you
> change the package name, only that you re-do the code.
>
> To be really explicit, name the thing
"Services_Technorati" and  
> name the
> class "Services_Technorati" .  The
PHP_Parser package is an  
> example of
> this kind of switch.  The first release 0.1 was
php4-compatible.  The
> upcoming release makes use of PHP_ParserGenerator and
is therefore
> PHP5+.  I didn't change the name of the package or
class, just the  
> contents.

Ah. That makes sense.

Thanks -- I've released an alpha.

James.

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