A challenge for us

> Same here.
> Sounds nice to start cooperating. How can I help?
>
> On Tue, Mar 16, 2010 at 10:28 PM, <[hidden email]> wrote:
> If I understand correctly, i.e., committing to one task per month I'm more than willing to help.
>
> What would be the protocol to cooperate on this?
>
> --
> Cesar Rabak
>
>
> Em 16/03/2010 04:21, Stéphane Ducasse < [hidden email] > escreveu:
> Hi
>
> I would like to initiative a task (monthly) for us. I would like to get really good tests coverage
> for some of the core classes. For example Date, Time, Duration, DateAndTime.
> This is really important in the long term to get sure that we identify bugs as soon as they appear.
>
> It would be really good if we could get team up and fix that together. Does anybody want to help?
>
> I started to fix some bugs there and write more tests in the process of fixing tests.
>
> Stef
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> It would be good to start checking for example the date and time tests.
> For example the readFrom: methods are ugly and it would be nice to access the tests and complement
> it if necessary. Adding nice categories and not as yet unclassified or Testing would be good.
>
> Stef
>
> On Mar 17, 2010, at 2:23 AM, Carla F. Griggio wrote:
>
>> Same here.
>> Sounds nice to start cooperating. How can I help?
>>
>> On Tue, Mar 16, 2010 at 10:28 PM, <[hidden email]> wrote:
>> If I understand correctly, i.e., committing to one task per month I'm more than willing to help.
>>
>> What would be the protocol to cooperate on this?
>>
>> --
>> Cesar Rabak
>>
>>
>> Em 16/03/2010 04:21, Stéphane Ducasse < [hidden email] > escreveu:
>> Hi
>>
>> I would like to initiative a task (monthly) for us. I would like to get really good tests coverage
>> for some of the core classes. For example Date, Time, Duration, DateAndTime.
>> This is really important in the long term to get sure that we identify bugs as soon as they appear.
>>
>> It would be really good if we could get team up and fix that together. Does anybody want to help?
>>
>> I started to fix some bugs there and write more tests in the process of fixing tests.
>>
>> Stef
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> On 18.03.2010 01:09, Germán Arduino wrote:
>
> I would like to help also, even when I'm with very little free time.
>
> To start I would like to understand how is the Pharo development
> process, being that (until now) I've mostly used RC2/3.
>
> The main doubts I've are:
>
> 1. The UNSTABLE version (the 1.1 right?) comes with no dev tools
> installed (OB, Shout, etc). Exist some metacello configuration to
> install all these tools? (I thinked that could be
> ConfigurationOfPharo, but seems that fail to install).
>
> Not all dev tools can be expected to be updated and work on a
> work-in-progress core image, thus we (well, at least I) make due with the
> good ol' system browser.
> Important packages will be updated and configurations working in 1.1 made
> available after API changes have been prohibited.
> That said, the O2Browser was updated a short time ago to work in 1.1 IIRC,
> your best bet for a more advanced browser would probably be to try and load
> a configuration of that.
>
> 2. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299),
> what is Pharo (pharo-dev) ? Is 1.0 RC2 with some tools?
>
> Pharo-dev is older versions of the core image, with tools equivalent to what
> is found in the RC-releases preloaded. (In fact, the latest release in that
> category is Pharo1.0-10508-rc2dev10.01.2.zip )
>
> 3. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299),
> what is Pharo1.1-64bit-Core? I mean, with which vm is supposed to be
> used?
>
> It's an image that has been run through the SystemTracer which converts it
> to 64bit format.
> You will be able to run it on the 64-64 version of the 5.0 Mac OSX VM's, not
> sure about the other platforms.
> Please note many of the vm-plugins are not 64bit clean, thus are likely to
> fail or crash your VM if used.
>
> 4. Some days ago I asked (with no response) about the Package Browser
> on RC2. I've found several mails talking about some problems between
> OB and O2, but I've not clear how to install it (I would like to have
> on 1.1 also).
>
> AFAIK, Alexandre and David spent some time a while ago to completely
> separate the model of O2 from that used by OB, thus resolving clashes caused
> by O2 overrides, now both should be able to be loaded at the same time in
> 1.0.
> (load with ConfigurationOfO2 in MetacelloRepository)
>
> Well, this is all for now, I will try also to read on the web page
> about repos and other things related with the Pharo development
> process.
>
> Thanks.
> Germán.
>
> There's only two repo's you really need:
> MetacelloRepository, for loading the tools you find useful (Really nice for
> checking issues with different tools in 1.1 as well)
> Inbox - Where you commit slices for inclusion in the next version.
>
> Cheers,
> Henry
>
> PS. The latest 1.0 release is PharoCore-1.0-10515rc3 (available from the
> gforge page), to get the equivalent of a Pharo (pharo-dev) rc image, load
> the ConfigurationOfPharo into that, and evaluate (ConfigurationOfPharo
> version: '1.0-rc.3-baseline') load.
>
> PPS. There will be an error when doing the load, since the AST-Tests package
> in squeaksource/rb has been renamed AST-Tests-Core, and the same for
> Refactoring-Tests, and the old packages removed...
> Lukas, would you mind uploading them again?
> For now, you can debug, and in the method that breaks, change the
> packageSpec's file to 'AST-Tests-Core-lr.8' and Refactoring-Tests-Core-lr.34
> respectively.
> This will happen twice, since the spec first loads
> ConfigurationOfRefactoringBrowser once as part of the defined packages, then
> again as a prereq when loading ConfigurationOfOmniBrowser.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Older versions have already stopped working twice now due to package deletions, first FFI, and then RB.
>
> F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in a 10508rc2 Core image will now fail.
>
> Cheers,
> Henry
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> I guess the correct incantation was (ConfigurationOfPharo project version:
> '1.0-rc3.10515') load. :)
> We really should set up a backup repository with all the packages included
> in specs though.
> Older versions have already stopped working twice now due to package
> deletions, first FFI, and then RB.
> F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in
> a 10508rc2 Core image will now fail.
> Cheers,
> Henry

> 2010/3/18 Henrik Johansen <[hidden email]>:
>>
>> I guess the correct incantation was (ConfigurationOfPharo project version:
>> '1.0-rc3.10515') load. :)
>> We really should set up a backup repository with all the packages included
>> in specs though.
>> Older versions have already stopped working twice now due to package
>> deletions, first FFI, and then RB.
>> F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in
>> a 10508rc2 Core image will now fail.
>> Cheers,
>> Henry
>
> I tried (ConfigurationOfPharo project version: '1.0-rc3.10515') load
> on 1.1UNSTABLE #11277 and
> fail with "TheWorldMenu class DNU #registerOpenCommand: "
>

> 2010/3/18 Henrik Johansen <[hidden email]>:
> >
> > I guess the correct incantation was (ConfigurationOfPharo project version:
> > '1.0-rc3.10515') load. :)
> > We really should set up a backup repository with all the packages included
> > in specs though.
> > Older versions have already stopped working twice now due to package
> > deletions, first FFI, and then RB.
> > F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in
> > a 10508rc2 Core image will now fail.
> > Cheers,
> > Henry
>
> I tried (ConfigurationOfPharo project version: '1.0-rc3.10515') load
> on 1.1UNSTABLE #11277 and
> fail with "TheWorldMenu class DNU #registerOpenCommand: "