RE: [PEAR-QA] Merging two classes
| From: | Lukas Smith | Date: | Tue, 02 Sep 2003 11:04:28 +0000 |
| Subject: | RE: [PEAR-QA] Merging two classes | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-175@lists.php.net to get a copy of this message | ||
> From: Lorenzo Alberton [mailto:l.alberton@quipo.it]
> Sent: Tuesday, September 02, 2003 1:34 AM
No need to CC PEAR Group as we all read the list anyways :-)
> I'd like to know how I should act in the
> following situation:
>
> In an effort to reduce the amount of alternative classes
> in PEAR (no, I'm not talking about Template engines,
> sorry :-), I managed to merge two packages I maintain.
>
> The two classes I'm talking about are Pager
> and Pager_Sliding. I already have refactored
> the two under the same package.
Ok, this is a good thing (tm)
> Now I'd like to release the new PEAR::Pager,
> which replaces the old one (don't worry, BC
> is kept @100%), and drop Pager_Sliding
> development as a standalone package.
Sounds fine to me.
> How should I proceed, though?
> My plan is to release a last version (with the last
> fixes from the previous release) of the 2 old packages,
> stating that they will be the last ones as "standalone"
> packages, and then release the new merged pkg.
>
> How can I declare the "death" of a package? An info
> in the README is enough?
> Should I document this in the pear manual? How?
Both sound like good ideas. In the manual you could just state that the
package is deprecated in favour of pager.
> What about version number? Should I increase
> the major version # even if there's no BC issue?
I would increase the major version number not only for BC breaks, but
also if you a lot of the underlying code changed. This can always result
in some surprising unintentional changes.
Regards,
Lukas