Crypt_RC4
| From: | Daniel O'Connor | Date: | Wed, 14 Jan 2009 23:37:20 +0000 |
| Subject: | Crypt_RC4 | ||
| Groups: | php.pear.qa | ||
| Request: | Send a blank email to pear-qa+get-5147@lists.php.net to get a copy of this message | ||
Crypt_RC4 is unmaintained.
Downloads stats say its fairly used (
http://pear.php.net/package-stats.php?pid=50&cid=6)
and there are
dependencies by other packages on this.
This makes me think: do a QA release, bump it to package.xml version 2.0,
etc.
Unfortunately, the author went and did a BC break in CVS -
http://osdir.com/ml/php.pear.qa/2005-04/msg00042.html
What's the best strategy here:
Plan 1:
- Create Crypt_RC42 (yeah, ick at name), and release that?
- Go back to the PHP4 branch, do a QA release with package 2.0 of that
(version 1.0.3)
- Have to investigate to see if bugs still exist that were fixed in
the other version, and fix them (probably do a 1.0.4 too that means)
Plan 2:
- Go back and remove all PHP 5 specifics (undo the PHP5 related BC break)
- Ensure the Crypt_RC4 API is backwards compatible
- Push out a 1.0.3 release, drop PHP5 compatibility
or something else?