Re: [Pharo-dev] Bad baseline practices
On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev@lists.pharo.org> wrote:
Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated?
Which project are you talking about?
Stephan
-- Cyril Ferlicot https://ferlicot.fr
Cyril Ferlicot <cyril.ferlicot@gmail.com> wrote:
On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev@lists.pharo.org> wrote:
Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated?
Which project are you talking about?
In a plain Pharo 7 image BaselineOfCalypso BaselineOfCommander BaselineOfSystemCommands Stephan
Am 16.01.2019 um 09:42 schrieb Stephan Eggermont <stephan@stack.nl>:
Cyril Ferlicot <cyril.ferlicot@gmail.com> wrote:
On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev@lists.pharo.org> wrote:
Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated?
Which project are you talking about?
In a plain Pharo 7 image
BaselineOfCalypso BaselineOfCommander BaselineOfSystemCommands
Stephan
Wasnât the problem that the wildcard notation is likely to hit the github API request limit? Norbert
On Wed, Jan 16, 2019 at 9:59 AM Norbert Hartl <norbert@hartl.name> wrote:
In a plain Pharo 7 image
BaselineOfCalypso BaselineOfCommander BaselineOfSystemCommands
In which version? Because in the latest I do not see any floating version. I know that Denis uses floating version but only for the development version, not for release.
Stephan
Wasnât the problem that the wildcard notation is likely to hit the github API request limit?
No, Denis is uring branches name v0.9.x for example to not use tags.
Norbert
-- Cyril Ferlicot https://ferlicot.fr
Hi Stephan. There was discussion about it. And idea is to have reproducible builds for Pharo. With floating versions we can't achieve it (at least with current tools). In addition I maintain floating branches for those projects (v0.15.x). So for your own projects you can reference them instead of static versions. ÑÑ, 16 Ñнв. 2019 г., 8:45 Stephan Eggermont stephan@stack.nl:
Cyril Ferlicot <cyril.ferlicot@gmail.com> wrote:
On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev@lists.pharo.org> wrote:
Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated?
Which project are you talking about?
In a plain Pharo 7 image
BaselineOfCalypso BaselineOfCommander BaselineOfSystemCommands
Stephan
participants (4)
-
Cyril Ferlicot -
Denis Kudriashov -
Norbert Hartl -
Stephan Eggermont