Gregory Beaver
2007-02-01 04:28:30 UTC
Hi all,
I've implemented a couple of things in the pear website, and plan to
make it live tomorrow. Please upgrade to 1.2.0RC1 and let me know if it
works for you, and commit any needed fixes right away. I plan to
release 1.2.0 stable in 24 hours so we can have a nice round
announcement date of February 1 for the changes.
What changes?
PEAR 1.3.6, package.xml 1.0 and pear.php.net's xmlrpc is going byebye.
package.xml 1.0 will be disallowed for all new releases effective
immediately, unless it is also paired with a package.xml 2.0.
pear.php.net's xmlrpc will be turned off on January 1, 2008, so peoples
will have 11 full months to upgrade before the big bang.
I also added a tool for developers on the package homepage that suggests
the next version number to release, and puts a really annoying
(blinking) warning if the last release used package.xml 1.0.
Let me stress: you only see these tools if you are logged in as a pear
developer, so it will not deter end users from using a package, they
won't even see the warning.
I also added a news item, and cleaned up the front page of the PEAR
website. In my opinion, it had WAY too much prose, and now is a cleaner
menu organized for users so they don't have to think so much just to
find what they're looking for.
Thanks,
Greg
I've implemented a couple of things in the pear website, and plan to
make it live tomorrow. Please upgrade to 1.2.0RC1 and let me know if it
works for you, and commit any needed fixes right away. I plan to
release 1.2.0 stable in 24 hours so we can have a nice round
announcement date of February 1 for the changes.
What changes?
PEAR 1.3.6, package.xml 1.0 and pear.php.net's xmlrpc is going byebye.
package.xml 1.0 will be disallowed for all new releases effective
immediately, unless it is also paired with a package.xml 2.0.
pear.php.net's xmlrpc will be turned off on January 1, 2008, so peoples
will have 11 full months to upgrade before the big bang.
I also added a tool for developers on the package homepage that suggests
the next version number to release, and puts a really annoying
(blinking) warning if the last release used package.xml 1.0.
Let me stress: you only see these tools if you are logged in as a pear
developer, so it will not deter end users from using a package, they
won't even see the warning.
I also added a news item, and cleaned up the front page of the PEAR
website. In my opinion, it had WAY too much prose, and now is a cleaner
menu organized for users so they don't have to think so much just to
find what they're looking for.
Thanks,
Greg