Update or replace module review?

A couple of years ago, I wrote a review of Algorithm::Diff, as it stood at that time. Since then, tye has taken over maintenance of the module, and made significant changes to its interface (see Algorithm::Diff icult to use for some discussion).

Yesterday I had a chance to use the module with its new interface for the first time. I'd like to update my review with information about the changes, but I don't really like the idea of tacking on an update at the bottom (the interface changes are significant, and deserve to be mentioned higher up in the writeup). Should I just replace most of the node, and add an explanation? I suppose I could post a reply, but that doesn't seem like a good solution either.

Any suggestions on clobber versus add-on?

Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.

Comment on Update or replace module review?

Replies are listed 'Best First'.
Re: Update or replace module review? by erix (Prior) on Jan 21, 2005 at 17:00 UTC
There is clobber and add-on, but is it not possible to add a second review root node, and put a reference to that new thread in the old root node? That would give separation of the two threads, keeping both accessible, while at the same time drawing attention to the fact that there are real differences in the API.	[reply]
Re: Update or replace module review? by Arunbear (Prior) on Jan 21, 2005 at 16:58 UTC
Since the interface has changed (significantly), why not post a new review incorporating the version number (or date) into the review title?	[reply]
Re: Update or replace module review? by mirod (Canon) on Jan 21, 2005 at 17:30 UTC
I would post a reply, and update the original node to mention the reply, giving the version numbers of the original review and of the new one. This way the module review is still at the same place, there is still only one review, and readers are informed about the update. You should also post the review to CPAN ratings, so it is accessible from search.cpan.org.	[reply]
Re: Update or replace module review? (update) by tye (Sage) on Jan 21, 2005 at 17:53 UTC
I still feel the same: Re: Maintaining module reviews (update). - tye	[reply]
Re: Update or replace module review? by Aristotle (Chancellor) on Jan 23, 2005 at 15:04 UTC
I'd write a new review node. An update to the old review is likely never to be seen by the majority of potential readers. Even a notifying reply to it is not likely to get a lot of attention. Not touching the old node also retains context for the chatter hanging off it. And finally, there's a reason we keep docs for old versions of things around, and I think that applies here as well. Just update the old review with a link to the new one at the top, saying that this review is for an old version of the module and not relevant for users of recent versions. Makeshifts last the longest.	[reply]