Though when I am making a significant content update, I will make it obvious with an "Update:" stamp. Unless I make the update within a few seconds after I post it (which, alas, I also do frequently).

I do try to take heed to replies, though, beforehand, so I don't change things that invalidate someone's reply and make them look stupid. That's just rude.

I'm not against such an option (it would be neat and I'd use it for minor updates that didn't just fix typos). But I'd rather have people follow-up to their own nodes rather than make a major update to an existing node. Or if the motivation behind the update was some other node, then follow-up to the motivating node and update your old node to include a link to your new node.

One exception might be possible long-lived nodes like one holding the source code for the Tk Chatterbox client, for example.

Reviews would be obvious candidates for that kind of update. Mentionning that the Camel 3 is obsolete because the Camel 4 is out and describes all about Perl 6 for example should really be in the main post, not in a follow-up

rather have people follow-up to their own nodes rather than make a major update to an existing node

Well, a problem with that is we don't see the text of the node which is being replied to (I think I made a suggested that we see them some time back). So, as it is now, if someone makes a new node to expand upon another node, you have to click on the New Node, then click on the node it is referencing. Too many clicks simply to get context, IMO.

hen follow-up to the motivating node and update your old node to include a link to your new node.

Well, if I already cleared that node from my queue, I don't know it was updated, which was my original point :)

Cheers,
KM

I was recently discussing this feature with myself (well, I asked if this would be plausible to implement but everyone ignored me :P). I think (without knowing much of the internals of PM) that this is a good idea.