The Pharo Consortium is very happy to announce that ÉTS Montréal has joined the
Consortium as an Academic Member.
About
- ÉTS Montréal: https://www.etsmtl.ca/en/Home
- Pharo Consortium: http://consortium.pharo.org
The goal of the Pharo Consortium is to allow companies and institutions to
Done!
On Thu, 23 Jan 2020 at 17:24 Martin Dias wrote:
> Done, thanks!
>
> On Tue, Jan 21, 2020 at 7:18 PM ducasse wrote:
>
>> Thanks!
>> Martin milton juraj should do it too :)
>>
>> S.
>>
>> On 21 Jan 2020, at 21:34, Alexandre Bergel
>> wrote:
>>
>>
>> *From: *Alexandre Bergel
>> *Subject:
There is a new Pharo build available!
The status of the build #23 was: SUCCESS.
The Pull Request #5572 was integrated:
"5571-testDefaultImageDoesNotStoreAnySetting-failing-in-Pharo9-on-CI-all-plattforms"
Pull request url: https://github.com/pharo-project/pharo/pull/5572
Issue Url:
How do we update https://files.pharo.org/image/80/stable-64.zip?
The "emergency evaluator on warning" issue [1] is fixed, but Launcher is
still serving a pre-fix image under "Official distributions". This seems
like a critical issue as new users may be immediately put off. FYI as a
workaround
There is a new Pharo build available!
The status of the build #25 was: SUCCESS.
The Pull Request #5537 was integrated: "Renraku Rules Profiles for Beginners -
fixes: #5536"
Pull request url: https://github.com/pharo-project/pharo/pull/5537
Issue Url:
We used #'pharo9.x' in smalltalkCI baseline and seems to work well:
https://github.com/hpi-swa/smalltalkCI/blob/master/repository/BaselineOfSmalltalkCI.package/BaselineOfSmalltalkCI.class/instance/setUpPharo5AndGreaterPackages..st
On Fri, Jan 24, 2020 at 5:47 PM ducasse wrote:
> Hi
>
> I would
Hi
I would like to adapt some baselines to Pharo90 and I’m wondering if we should
not
add pharo9.x to a list somewhere.
S.
EstebanLM wrote
> Done
I see the new 8.0.1 release tag, but the URL still downloads 8.0.0
(bbcdf97). Is there another step?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Done
> On 24 Jan 2020, at 17:57, Sean P. DeNigris wrote:
>
> How do we update https://files.pharo.org/image/80/stable-64.zip?
>
> The "emergency evaluator on warning" issue [1] is fixed, but Launcher is
> still serving a pre-fix image under "Official distributions". This seems
> like a
thanks esteban.
We should take the time to bullet proof our process.
S.
> On 25 Jan 2020, at 08:33, Esteban Lorenzano wrote:
>
> Mmm. There is an error in the CI and it did not uploaded the stable*.zip
> archives (while it did the latest).
> I uploaded them by hand but we need to review
There is a new Pharo build available!
The status of the build #24 was: SUCCESS.
The Pull Request #5569 was integrated:
"5562-Executing-All-Instances-in-the-startup-affects-loading-times"
Pull request url: https://github.com/pharo-project/pharo/pull/5569
Issue Url:
Which url?
I don’t know well how pharo launcher works, but zeroconf is downloading the
correct version.
but there is a bug somewhere and the naming/versioning still shows 8.0.0 while
it should show 8.0.1.
Esteban
> On 24 Jan 2020, at 22:31, Sean P. DeNigris wrote:
>
> EstebanLM wrote
>>
Mmm. There is an error in the CI and it did not uploaded the stable*.zip
archives (while it did the latest).
I uploaded them by hand but we need to review the process (problem is now I
cannot test it in my machine anymore, I need to prepare an environment)
> On 25 Jan 2020, at 07:30, Esteban
Thanks.
For me I cannot get the phar9.x branch loading. I will investigate if I can
understand what is the problem
aselineOfCozy >> baseline: spec [
spec for: #'pharo8.x'
do: [
spec package: 'CozyCommon'.
14 matches
Mail list logo