We can yet know which packages load in Pharo 1.2 / 1.3, .... it's written
in the

ConfigurationOf......>>stable: spec
<symbolicVersion: #stable>
 spec for: #'pharo1.2.x' version: '1.0'.
spec for: #'pharo1.3.x' version: '1.1'.


Would be nice / necessary to script upcoming SmalltalkHub and render
automatically the compatibility list. Automatic dashboard and good
indicators are the first step.

Second nice step would be automatic testing that each ConfigurationOf
 loads according according to what is declared. Jenkins to the rescue.

It seems stable API is always subject to controversy and will slow down the
release process. Pharo already has a deprecation policy.

I do not see the point of taking a 5 years old package and expect to load
it correctly in current Pharo (especially in an open source platform).
Custom solutions mixing old, new and legacy stuff will always be a pains
and lot of work, stable API or not - except (maybe) when high test coverage
is present (at least it's far easier).

Now I believe in fixed length iteration that provide some answers to moving
packages from one version to another. Example:
- 4 months development of Pharo (new features)
- 1 / 2 months feature freeze and fix - now guys upgrade your packages we
won't break things anymore.
- write announcements and release.

Good process, automation and visibility is one key for me.

Laurent


On Thu, Dec 29, 2011 at 3:44 PM, Benoit St-Jean <[email protected]> wrote:

> I was wondering what is planned regarding packages available on
> SqueakSource and Pharo.  More and more packages can't load in Pharo and it
> gets more and more frustrating not being able to load anything without
> having to add/modify methods/classes all over the place so those packages
> can load properly in Pharo.  Are we looking at a Pharo-only kind of
> SqueakSource in the future ?
>
> Besides, having to handle platform specific (i.e. Pharo vs Squeak) for
> every package is adding more complexity than what is needed.  I know
> backward compatibility was thrown away from the start to avoid compromises
> in Pharo but how do we take care of the fact that as each day passes, less
> and less stuff from SqueakSource is usable in Pharo ?
>
> tia
>
> -----------------
> Benoit St-Jean
> Yahoo! Messenger: bstjean
> A standpoint is an intellectual horizon of radius zero.
> (Albert Einstein)
>
>

Reply via email to