- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Issue Tracker] Call for CleanUp of the issue tracker

by Marcus Denker

On 17 Sep 2014, at 13:02, Nicolai Hess <nicolaihess(a)web.de> wrote: > Yes but, > > 2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hello, > > There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦). > > A lot of those issues are very old. A lot are in a bad shape: > > -> not reproducible > -> *completely* unclear what action could lead to solve the issue > -> outdated (e.g. small improvements submitted ages ago, but even > the author does not care to submit a new version for Pharo4) > > I think we should be more radical in closing issues. If someone submits something > but can not even answer a simple question in 2 months â> this is the same as âI donât careâ. > > 2 months are to short. 4 or maybe 6. Yes, you are right 6 months is good. The idea is that the issue will be closed, but with a mail to the âownerâ of the issue so that he/she can decide to re-openâ¦ and âwill work on that laterâ would be a valid answer. > There are open issues without any action on our part - for months. And that does > not mean "we don't care". If someone reports an issues and don't > have the time to react on comments/questions for a couple of months, I understand that. > > > nicolai > > > So *PLEASE*: > > -> check all the issue that *you* submitted. Are they still relevant? Is there enough > information for anyone to do anything? > -> check all the issues you where involved with in discussions. It is much easier for > you than for me to understand what the conclusion of the discussion is. > -> help checking *old* entries. Is is still relevant? What is the next action? > > +1 > > > > > Marcus >

Sept. 17, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40230 Home: https://github.com/pharo-project/pharo-core

Sept. 17, 2014

[pharo-project/pharo-core] ce818b: 40230

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ce818b3f743a0a0c94d86ec1471873b2a79c65ab https://github.com/pharo-project/pharo-core/commit/ce818b3f743a0a0c94d86ec1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-17 (Wed, 17 Sep 2014) Changed paths: R Graphics-Display Objects.package/ColorForm.class/instance/color manipulation/ensureTransparentColor.st M ScriptLoader40.package/ScriptLoader.class/instance/ci/compileNewUpdateMethodSilentlyPreLoad_postLoad_.st A ScriptLoader40.package/ScriptLoader.class/instance/ci/publicChangesSilently_user_password_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script230.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40230.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40230 14027 ensureTransparentColor is unused and looks dead https://pharo.fogbugz.com/f/cases/14027 http://files.pharo.org/image/40/40230.zip

Sept. 17, 2014

Re: [Pharo-dev] [Issue Tracker] Call for CleanUp of the issue tracker

by Nicolai Hess

Yes but, 2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hello, > > There are right now 675 open issues. (we managed to close 63 just the > last 7 daysâ¦). > > A lot of those issues are very old. A lot are in a bad shape: > > -> not reproducible > -> *completely* unclear what action could lead to solve the issue > -> outdated (e.g. small improvements submitted ages ago, but even > the author does not care to submit a new version for Pharo4) > > I think we should be more radical in closing issues. If someone submits > something > but can not even answer a simple question in 2 months â> this is the same > as âI donât careâ. > 2 months are to short. 4 or maybe 6. There are open issues without any action on our part - for months. And that does not mean "we don't care". If someone reports an issues and don't have the time to react on comments/questions for a couple of months, I understand that. nicolai > > So *PLEASE*: > > -> check all the issue that *you* submitted. Are they still relevant? > Is there enough > information for anyone to do anything? > -> check all the issues you where involved with in discussions. It is much > easier for > you than for me to understand what the conclusion of the discussion is. > -> help checking *old* entries. Is is still relevant? What is the next > action? > +1 > > > Marcus >

Sept. 17, 2014

[ANN] SciSmalltalk v0.14

by Serge Stinckwich

Dear all, we are to happy to announce SciSmalltalk v0.14 SciSmalltalk is a new Smalltalk project, similar to existing scientific libraries like NumPy, SciPy for Python or SciRuby for Ruby. SciSmalltalk already provide the following basic functionalities: - complex and quaternions extensions, - random number generators, - fuzzy algorithms, - Didier Besset's numerical methods, - Ordinary Differential Equation (ODE) Solver. Version 0.14 includes new work from Werner Kassens about function fittings: https://github.com/SergeStinckwich/SciSmalltalk/wiki/Math-FunctionFit and math accuracy framework: https://github.com/SergeStinckwich/SciSmalltalk/wiki/Math-AccuracyFramework SciSmalltalk project web page is here: https://github.com/SergeStinckwich/SciSmalltalk All the code is available under the MIT licence. We have more than 506 green unit tests and we run a CI job here: https://ci.inria.fr/pharo-contribution/job/SciSmalltalk/ This version should work on Pharo 3.0/4.0 and also Squeak 4.5 (to be confirmed). We are a small community, we are looking for more volunteers to contribute code and documentation. Please join us at : https://groups.google.com/forum/#!forum/scismalltalk -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Thierry Goubier

All the repository types have that option. Thierry 2014-09-17 11:37 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > What kind of repo is that? > > Stephan > >

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Stephan Eggermont

What kind of repo is that? Stephan

Sept. 17, 2014

[Issue Tracker] Call for CleanUp of the issue tracker

by Marcus Denker

Hello, There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦). A lot of those issues are very old. A lot are in a bad shape: -> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4) I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ. So *PLEASE*: -> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action? Marcus

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by phil＠highoctane.be

I think that I've found why it got slow like that. I had the store diff instead of full versions (mistakenly selected I guess) and switching things back did the trick. What's that option? Never noticed it and it for sure hurt or plain doesn't work. Phil On Wed, Sep 17, 2014 at 11:18 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Is it caught in a kind of loop trying to find the base version? Scanning > through the ancestors and adding all those to the package cache? > > Thierry > > 2014-09-17 11:07 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Filesize is around 1MB. >> >> Here is what I do get in the debugger when stopping. >> >> TIA >> Phil >> >> >> >> >> On Wed, Sep 17, 2014 at 11:02 AM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Hi Phil, >>> >>> how large is your package? We talked about very large packages with >>> Sebastian Sastre not so long ago. >>> >>> Can you interrupt it to see where it is stuck? >>> >>> Thierry >>> >>> >>> 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>> >>>> Monticello kinds of freezes my image for a *very* long time. >>>> Long, meaning that it never completes I guess. >>>> >>>> Memory use shoots through the roof. >>>> >>>> What could cause that? >>>> >>>> I have been saving more than 200 versions of my package. >>>> >>>> Thanks for some advice from the trenches. >>>> >>>> Phil >>>> >>> >>> >> >

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Thierry Goubier

Is it caught in a kind of loop trying to find the base version? Scanning through the ancestors and adding all those to the package cache? Thierry 2014-09-17 11:07 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Filesize is around 1MB. > > Here is what I do get in the debugger when stopping. > > TIA > Phil > > > > > On Wed, Sep 17, 2014 at 11:02 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Phil, >> >> how large is your package? We talked about very large packages with >> Sebastian Sastre not so long ago. >> >> Can you interrupt it to see where it is stuck? >> >> Thierry >> >> >> 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> >>> Monticello kinds of freezes my image for a *very* long time. >>> Long, meaning that it never completes I guess. >>> >>> Memory use shoots through the roof. >>> >>> What could cause that? >>> >>> I have been saving more than 200 versions of my package. >>> >>> Thanks for some advice from the trenches. >>> >>> Phil >>> >> >> >

Sept. 17, 2014