Adrian: Thanks for your changes! It looks much better :) Laufert: yes, that's a cool idea. I wasn't aware neither.
Could someone write a template? Then we just add the link to the new page. Cheers Mariano On Thu, Dec 3, 2009 at 10:44 AM, Adrian Lienhard <[email protected]> wrote: > ah, I didn't know that is possible. Good idea! > > Adrian > > On Dec 3, 2009, at 10:34 , laurent laffont wrote: > > > May be you should fill the issue templates on google code issue > > tracker. > > Like this: http://code.google.com/p/chromium/issues/entry > > > > Laurent > > > > > > On Thu, Dec 3, 2009 at 10:18 AM, Adrian Lienhard <[email protected]> > > wrote: > > > >> Thanks Mariano. I have condensed your text a bit and put it online at > >> http://www.pharo-project.org/community/issue-tracking > >> > >> Cheers, > >> Adrian > >> > >> BTW, I also added the milestones for version 1.1 on the home page. > >> > >> On Dec 2, 2009, at 18:43 , Mariano Martinez Peck wrote: > >> > >>> I think it is really a good idea to create a page in the Pharo > >>> website about > >>> how to report a bug. I think that only the link to the google page > >>> is not > >>> enough. Maybe it is a good idea to explain it a bit more, and in > >>> addition, > >>> give some tips. I would write something like the text above in that > >>> page. I > >>> would replace everywhere where it is a link to > >>> http://code.google.com/p/pharo/issues/list to this new page. I saw > >>> there > >>> are these > >>> > >>> http://www.pharo-project.org/home (on the right) > >>> http://www.pharo-project.org/documentation/faq (in the question > >>> "Where do I > >>> report Pharo bugs?") > >>> > >>> My English is not the best at all, so any feedback is more than > >>> welcome. In > >>> addition, maybe you don't agree with me. > >>> > >>> My main purpose is to help newcomers to submit issues. > >>> > >>> So....here it is > >>> > >>> > >>> " > >>> An issue, also known as ticket, represents many things. It can be a > >>> bug, a > >>> enchantment, packages, projects or commits to check, etc. > >>> For the Pharo project, we use the Google Code issue tracker which is > >>> in > >>> http://code.google.com/p/pharo/issues/list. > >>> > >>> - Before submitting you may take into account the following tips: > >>> > >>> 1) Search in the existent issue list if there is something similar. > >>> In the > >>> issue tracker you will find a "search" button to do that. Be aware > >>> that > >>> there is a list of options and the default one is "Open ticket". It > >>> is very > >>> common you need to search in "All issues". > >>> > >>> 2) If the ticket is a bug, and there is a problem with certain > >>> method, > >>> search for that method or even for that class. It is very common to > >>> have > >>> "MessageNotUnderstood". So, in this case you can search for that > >>> method. For > >>> example, if you evaluate: > >>> > >>> TestCase nonExistentMethod: something other: another > >>> > >>> You will get "MessageNotUnderstood: TestCase > >>> class>>nonExistentMethod:other:" > >>> > >>> So, here you can search for "nonExistentMethod:other:" for exampe. > >>> > >>> 3) Do the same of 1) and 2) but on the mailing list. If you are new > >>> or even > >>> if you are not subscribed, you can see and search in the mailing > >>> list here: > >>> http://n2.nabble.com/Pharo-Smalltalk-f2305563.html > >>> > >>> Sometimes some tickets are reported only in mailing list (that's too > >>> bad!!!). And maybe, that happened before you get subscribed in the > >>> mailing > >>> list. This way you are sure you are searching also in the mailing > >>> list. > >>> > >>> > >>> - When you are submitting an issue there are also some tips you > >>> should take > >>> into account: > >>> > >>> 1) If the issue is related to ClassBrowser, refactor or similar, > >>> please tell > >>> us which browser are you using. If you don't know it, just evaluate > >>> and see > >>> the results of "SystemBrowser default". > >>> > >>> 2) ALWAYS say which version of VM, image (not only if it is a core > >>> or pharo > >>> image but also exactly the version) and OS are you using. > >>> > >>> 3) If the bug is reproducible, please explain how to do it step by > >>> step. If > >>> we have to use a particular VM, OS, or image, say it. > >>> > >>> 4) If the bug brings a debugger popup, it would be very useful if > >>> you could > >>> put in the issue entry the full stacktrace. To get this stacktrace, > >>> there > >>> are 2 ways: > >>> > >>> 4.a) Search for the generated PharoDebug.log which is in the same > >>> directory > >>> where if image is and attached in the issue. In that file there is > >>> not only > >>> the full stacktrace but also some information about the version of > >>> the VM, > >>> OS and image you were using at that moment, etc. > >>> > >>> 4.b) In the debugger, open the contextual menu and there is an item > >>> 'mail > >>> out bug report' to directly send the stack trace with VM version etc > >>> to the > >>> pharo list (or whoever you want to, but by default it's the Pharo > >>> ml). Of > >>> course you can edit the message to describe your problem for > >>> example. > >>> > >>> 5) If you are not a newcomer and you know a bit you can put labels > >>> to the > >>> issue. For example if it should be Milestone 1.0 or Type-Closure, or > >>> TypeOB, > >>> etc. > >>> > >>> 6) If you are not a newcomer and you know a bit you can copy people > >>> with the > >>> "Cc:" option. This is very useful when you know that the issue is > >>> in a > >>> certain package for example and you know who is responsible or > >>> maintainer of > >>> it. > >>> > >>> 7) After submitting the issue, you must send and email to the > >>> mailing list > >>> with the link. What you can do also is to copy and paste the details > >>> of the > >>> issue in the body of the email. With this, all the people know about > >>> it. > >>> > >>> 8) If the ticket is a MNU it would be very useful to put that > >>> message (in > >>> our example "MessageNotUnderstood: TestCase > >>> class>>nonExistentMethod:other:") in the description of the ticket > >>> or even > >>> in the title of the issue and the subject of the email. With this we > >>> can > >>> take advantage of the Google search engine. > >>> > >>> 9) If you have a fix remember you must sign the MIT license first. > >>> For more > >>> information read http://www.pharo-project.org/license > >>> > >>> " > >>> > >>> On 2 déc. 2009, at 08:05, Mariano Martinez Peck wrote: > >>> > >>> > >>> > >>> 2009/12/2 laurent laffont <[email protected]> > >>> > >>>> Hello, > >>>> > >>>> I want to check if there's updates to Slime package as I faces > >>>> several bugs > >>>> but sources.lukas-renggli.ch seems to be down. Is there a mirror ? > >>>> > >>>> > >>>> About the bugs (Slime-lr.24,current pharo rc1 web image), when I > >>>> select > >>>> refactor > code critics: > >>>> > >>>> - it seems that ParserTreeSearcher has been renamed to > >>>> RBParserTreeSearcher. Thus there's several errors like > >>>> WAChangesStateWhileRenderingRule>>initialize (ParseTreeSearcher is > >>>> Undeclared) > >>>> > >>>> - this done, I have the error: > >>>> AnObsoleteParseTreeSearcher(Object)>>doesNotUnderstand: > >>>> #executeTree:initialAnswer: (from > >>>> RBAssignmentIfTrueRule>>checkMethod:) > >>>> > >>>> > >>>> How do I save a stack trace to a text file (or clipboard) from the > >>>> debugger > >>>> ? > >>>> > >>> > >>> Look for the file called PharoDebug.log which is in the directory > >>> where the > >>> image is. It will have not only the stacktrace but also much more > >>> information, as VM version, OS, etc. > >>> > >>> > >>> > >>> or.... > >>> > >>> In the debugger, open the contextual menu and there is an item 'mail > >>> out bug > >>> report' to directly send the stack trace with VM version etc to the > >>> pharo > >>> list (or whoever you want to, but by default it's the Pharo ml). Of > >>> course > >>> you can edit the message to make it shorter (we dont need the full > >>> stack in > >>> general) and describe your problem etc. > >>> > >>> > >>> > >>> Best, > >>> > >>> Mariano > >>> > >>> > >>>> > >>>> > >>>> Regards, > >>>> > >>>> Laurent Laffont > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> [email protected] > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> [email protected] > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> > >>> -- > >>> Simon > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> [email protected] > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> [email protected] > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> [email protected] > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
