Description: ------------ Editing bug #11294, on 2007-06-12 15:40 UTC, I changed the status, added a comment, and corrected the package from Structures_DataGrid_Renderer_Pager to Pager. I'm a maintainer of the former but not of the later. However, I did not receive any mail for this action, although I received previous ones, when the package was still Structures_DataGrid_Renderer_Pager. Then quipo, a Pager's maintainer, made a change to this bug, and I did not receive any mail, as well. However, I wanted to continue monitoring this bug, which I consider important. So I came back, to manually check what was going on, and saw quipo's change. I then chose to "Edit" the bug, made a change, and still no mail. Once a developer has posted a comment or made any change to a given bug, is it possible he always receive follow-ups, whether the package changes, whether he's (still) a maintainer or not?

or you can use the subscribe feature ? iirc you can subscribe via your nick, doing auto subscribing is bad, perhaps if I make a comment to bug X and Y then that doesn't mean I want to monitor it

I understand your point. It's arguable, but maybe that for people handling many bugs, auto-subscribing is a bad thing. However, maybe that you could make it clearer that one can subscribe with a nick and not only an email.

Helgi is right: Changing the package does not mean that somebody wants to get notified about changes. Using the subscribe feature is the better solution. This feature only accepts email addresses, but not PEAR accounts (there is a regular expression that checks the entered address). I allowed myself to change the summary of this report. The original problem doesn't need to be fixed (according to the discussion), but the subscription feature is a little bit broken: The user does not any feedback about the (un)subscription. Neither a confirmation message nor the generated error message are shown. ($errors array is filled, but not shown; I haven't investigated why yet.)

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.