[Pharo-project] Call: identifying issues relevant for 1.0
Hi all, With Marcus I went through the list of open issues and we tagged the ones we think need to be done for 1.0. We may have missed some important ones. So this is now to ask if *you* have any other issues that you think should be integrated into 1.0. Please post them here so that we can discuss and update the bug tracker. I'd like to soon freeze the list and after this only add critical bugs as 1.0-tagged issues. When we go beta (and I hope this will be possible in the next few weeks), no new features or changes will be added anymore. Thanks, Adrian ___________________ http://www.adrian-lienhard.ch/
I know it is quite a job, but I would like to see the core debugger fixed and maintained - or removed. #709 is a serious issue unless someone has recently fixed it. I have not used the OB one too much, so I guess it comes down to a discussion of what the official tool-set actually is for Pharo. I don't think we really have the bandwidth to maintain two toolsets, but we are currently keeping them around. thanks, Mike
the core debugger is important and it will continue to be important. stef On Jul 5, 2009, at 1:06 PM, Michael Roberts wrote:
I know it is quite a job, but I would like to see the core debugger fixed and maintained - or removed. #709 is a serious issue unless someone has recently fixed it. I have not used the OB one too much, so I guess it comes down to a discussion of what the official tool-set actually is for Pharo. I don't think we really have the bandwidth to maintain two toolsets, but we are currently keeping them around.
thanks, Mike
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I second that. Added the tag 1.0 to #709. Adrian On Jul 5, 2009, at 20:11 , Stéphane Ducasse wrote:
the core debugger is important and it will continue to be important.
stef
On Jul 5, 2009, at 1:06 PM, Michael Roberts wrote:
I know it is quite a job, but I would like to see the core debugger fixed and maintained - or removed. #709 is a serious issue unless someone has recently fixed it. I have not used the OB one too much, so I guess it comes down to a discussion of what the official tool- set actually is for Pharo. I don't think we really have the bandwidth to maintain two toolsets, but we are currently keeping them around.
thanks, Mike
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
thanks, i would definitely like to see the core tools maintained and the debugger is a fun project. I just wonder that since I spend most of the time in the core image, i am not helping maintaining Pharo itself, just the core bit. I hope that our toolset (the super-toolset across both images) as it matures becomes more modular and well factored. I guess i'm just concerned about maintaining two debuggers, since it's non-trivial. Perhaps one could be a super or subset of the other? I don't know. cheers, Mike
Mike, The rebuttal position: someone not long ago reported having to disable the OB debugger in order to "be able to use Pharo." FWIW, I was having some problems myself, and changed debuggers based on that report. My problems might have been due to a corrupted image, so changing debuggers might have been irrelevant to my ultimate climb out of the hole by building a new image. Your point about not spreading ourselves too thin is well taken, but I also wonder whether we should expect to have high end tools and a set with more modest demands on the cpu. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Roberts Sent: Sunday, July 05, 2009 6:06 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Call: identifying issues relevant for 1.0 I know it is quite a job, but I would like to see the core debugger fixed and maintained - or removed. #709 is a serious issue unless someone has recently fixed it. I have not used the OB one too much, so I guess it comes down to a discussion of what the official tool-set actually is for Pharo. I don't think we really have the bandwidth to maintain two toolsets, but we are currently keeping them around. thanks, Mike _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (4)
-
Adrian Lienhard -
Michael Roberts -
Schwab,Wilhelm K -
Stéphane Ducasse