> On 08 Jun 2017, at 09:36, Diego Lont wrote:
>
> Hi all,
>
> To keep the common projects in smalltalkhub stable, we agreed that those
> should use symbolic versions like release3 // release3.5 etc. This way we can
> add bug fixes and avoiding loading of different versions through different
Hi all,
To keep the common projects in smalltalkhub stable, we agreed that those should
use symbolic versions like release3 // release3.5 etc. This way we can add bug
fixes and avoiding loading of different versions through different projects.
But I might have done something stupid to the confi
On 06/07/2017 03:46 AM, Holger Freyther wrote:
On 7. Jun 2017, at 14:09, Stephan Eggermont wrote:
Never refer to fixed versions unless you know why (you need to avoid a
specific bug fix).
When wanting to have repeatable builds (e.g. for bugfixes) and in the
absence of other means to lock/def
> On 7. Jun 2017, at 14:09, Stephan Eggermont wrote:
>
> Never refer to fixed versions unless you know why (you need to avoid a
> specific bug fix).
When wanting to have repeatable builds (e.g. for bugfixes) and in the
absence of other means to lock/define versions externally, I think using
a f
I would like to repeat here again: don't refer to fixed version numbers
of packages out of your control in configurations. Refer to #'release'
versions that can be patched by the maintainers of your dependencies.
That is only appropriate when having to patch around a problem, and
couples your c
On 07/06/17 06:19, Holger Freyther wrote:
Hi,
after having made some new releases I have an odd Metacello issue and
I am not sure how to debug it. This happens on my legacy
Pharo3/Pharo4 images that I still need to support in deployment.
It seems to be related to a dependency chain of
"app"->Vo
Hi,
after having made some new releases I have an odd Metacello issue and I am not
sure how to debug it. This happens on my legacy Pharo3/Pharo4 images that I
still need to support in deployment.
It seems to be related to a dependency chain of "app"->VoyageMongo->Magritte3
3.5.0 and somehow ve
