June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Something does not work with issue tracker status

by Igor Stasenko

On 6 June 2012 23:40, Camillo Bruni <camillobruni(a)gmail.com> wrote: > we should first get the test monkey up and running... > that will take a lot of work an assures that at least the existing tests won't fail! yes. and second thing, even if we integrate half-backed solution, we can always fix it on next iteration, if it causing problems.. like that it will be some progress comparing to indefinite time when issue needs to be reviewed. but sure thing, for changes which can really screw things up, we need serious review before integration. -- Best regards, Igor Stasenko.

June 7, 2012

[Pharo-project] Pharo-1.4-Tests Â» 32,win - Build # 61 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 6, 2012

Re: [Pharo-project] FilePlugin changed it's behavior?

by Igor Stasenko

On 6 June 2012 21:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> is not failing as it says it should in the comment. >> >> Has this behavior changed lately? Â Should this be fixed in the vm side, wait for NativeBoost? Or we should just by now fix the comment and clients not to expect that? > > I think that we should put all our eggs in the same basket :) so the non native boost version should work too. Sorry for confusion.. the thing we did with NB was just a mere experiment.. File plugin should work without NB or with it.. out of the question. >> some pointer? -- Best regards, Igor Stasenko.

June 6, 2012

Re: [Pharo-project] Fuel

by Igor Stasenko

Yeah.. we even can make a lint rule: - 1 max reference per package to class from another package unless referencing class belongs to kernel modules.. they are so easy to do, if everyone would follow that rule :) On 6 June 2012 22:54, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Steph wants less hardcoded references to PackageInfo :) > > > On Wed, Jun 6, 2012 at 10:51 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hmm I didn't catch it >> >> Martin >> >> On Wed, Jun 6, 2012 at 4:47 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> > ok for me >> > I'm studying PackageInfo and the rest to see what I can do. >> > >> >> mariano/martin >> >> >> >> Â Â Â Â I would like to extract PakageInfo into self packageInfo in the >> >> fuel code. >> >> >> >> Yes, I like that the idea. I guess you are talking about >> >> FuelPackageLoader in #named: and #withPacakges: right? >> >> What about calling it direclty #package? Â so that we may be able to >> >> change it later to PackageInfo or RPackage or whatever? >> >> >> >> >> >> Can I do it? >> >> >> >> Stef >> >> >> >> >> >> >> >> >> >> -- >> >> Mariano >> >> http://marianopeck.wordpress.com >> >> >> > >> > >> > -- Best regards, Igor Stasenko.

June 6, 2012

Re: [Pharo-project] Something does not work with issue tracker status

by Camillo Bruni

we should first get the test monkey up and running... that will take a lot of work an assures that at least the existing tests won't fail!

June 6, 2012

Re: [Pharo-project] Fuel

by Guillermo Polito

Steph wants less hardcoded references to PackageInfo :) On Wed, Jun 6, 2012 at 10:51 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hmm I didn't catch it > > Martin > > On Wed, Jun 6, 2012 at 4:47 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > ok for me > > I'm studying PackageInfo and the rest to see what I can do. > > > >> mariano/martin > >> > >> I would like to extract PakageInfo into self packageInfo in the > fuel code. > >> > >> Yes, I like that the idea. I guess you are talking about > FuelPackageLoader in #named: and #withPacakges: right? > >> What about calling it direclty #package? so that we may be able to > change it later to PackageInfo or RPackage or whatever? > >> > >> > >> Can I do it? > >> > >> Stef > >> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > >

June 6, 2012

Re: [Pharo-project] Fuel

by Martin Dias

Hmm I didn't catch it Martin On Wed, Jun 6, 2012 at 4:47 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ok for me > I'm studying PackageInfo and the rest to see what I can do. > >> mariano/martin >> >> Â Â Â Â I would like to extract PakageInfo into self packageInfo in the fuel code. >> >> Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? >> What about calling it direclty #package? Â so that we may be able to change it later to PackageInfo or RPackage or whatever? >> >> >> Can I do it? >> >> Stef >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

June 6, 2012

Re: [Pharo-project] FilePlugin changed it's behavior?

by StÃ©phane Ducasse

> is not failing as it says it should in the comment. > > Has this behavior changed lately? Should this be fixed in the vm side, wait for NativeBoost? Or we should just by now fix the comment and clients not to expect that? I think that we should put all our eggs in the same basket :) so the non native boost version should work too. > some pointer? > > Tx

June 6, 2012

Re: [Pharo-project] Fuel

by StÃ©phane Ducasse

ok for me I'm studying PackageInfo and the rest to see what I can do. > mariano/martin > > I would like to extract PakageInfo into self packageInfo in the fuel code. > > Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? > What about calling it direclty #package? so that we may be able to change it later to PackageInfo or RPackage or whatever? > > > Can I do it? > > Stef > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 6, 2012

Re: [Pharo-project] Something does not work with issue tracker status

by phil＠highoctane.be

Why not organize "feature teams" along packages or package sets on which experts have approval power? Of course, some stuff will be cross packages but still, it should work. Is there any chart or trend in there, like bugs unfixed since x days that should be? Phil 2012/6/6 Sean P. DeNigris <sean(a)clipperadams.com> > > Mariano Martinez Peck wrote > > > > We really need people helping review changes... So, please, help us > review > > issues. Is the only way > > to improve. > > > > +1. I will try a few... > > Sean > > -- > View this message in context: > http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp4… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

June 6, 2012