Hi there, I have a couple of questions about Systemtools (Messagebrowser, Browser, Changesorter ...). Is there roadmap for pharo3, on what are you working, what should work for the next release. I filed (and fixed) some bugs. And have some more. But I don't want to do this if some of the tools may be deprecated or will be replaced. I read the Pharo2 and 3 changelog, but I am still unsure, and before I make unneeded bug reports: There are some bugs on MessageBrowser: Time stamp from source/byte code /time stamp-combo doesn't work. MessageBrowser doesn't play well with RGCommentDefinition as search results: Textpanel tries to parse comments as code (this is an old bug, even recent squeak versions) Browse senders/Implementers doesn't make sense /doesn't work for comments Browse Version does not work for comments No menu on comment entries. MNU if exactly one entry is found Some of these issues aren't new and there were already discussions for the older FlatMessageList.(issue 5860<https://pharo.fogbugz.com/default.asp?5860>). Work on dualchangesorter seems to be half-done (menu-handling broken). (no one uses dualchangesorter nowadays?) It distract me a bit that the completion menu *in spotlight* shows codecompletion that *spotlight can not find* (class vars for example). and more. I am not a total novice, but more than most of you. And so I may stumble across some issues, that you don't encounter in your workflow. (Otherwise I can not explain why there are no bug reports for these issues :-). Am I free in reporting all kind of bugs or is this "too much noise". Btw, what about Pharo2.0, is this release freezed, or can/should issues be reported and fixed for Pharo2.0 as well? regards Nicolai