PharoLauncher mac download not the latest version
So I re downloaded PharoLauncher using this link https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/lastSuc... and it is not the latest version as it does not contain the latest commit which is my commit with the new progress bar. At first I thought that it was loading something else than bleedingEdge configuration but I don't see anything else in the ConfigurationOfPharoLauncher. Am I doing something wrong ?
kilon alios wrote:
So I re downloaded PharoLauncher using this link
https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/lastSuc...
and it is not the latest version as it does not contain the latest commit which is my commit with the new progress bar. At first I thought that it was loading something else than bleedingEdge configuration but I don't see anything else in the ConfigurationOfPharoLauncher. Am I doing something wrong ?
Notice at [1] that its upstream trigger is [2] which has no upstream project, and all builds have been started by Damien by hand (hover over the person icons). I guess the approach is that uploads to the PharoLauncher repository can be fairly unrestricted, with only the risk only of breaking [3] as the bleeding edge CI job (also trigger by Pharo bleeding edge updates). I like this approach since it helps collaboration and review of changes, with less fear uploading a change will break the world, with more quality control applied to [1] as a "Release" mechanism. [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/ [2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage/ [3] https://ci.inria.fr/pharo-contribution/job/PharoLauncher/ cheers -ben
ah ok yes I realised that it was a complex process one build triggering the other build but I did not notice it was triggered manually. Yes I agree thats a good idea but I expected this control to be at Configuration level by having a "stable" release. On Wed, Sep 10, 2014 at 12:25 PM, Ben Coman <btc@openinworld.com> wrote:
kilon alios wrote:
So I re downloaded PharoLauncher using this link https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/ lastSuccessfulBuild/artifact/pharo-ci/Pharo%203.0.0.dmg
and it is not the latest version as it does not contain the latest commit which is my commit with the new progress bar. At first I thought that it was loading something else than bleedingEdge configuration but I don't see anything else in the ConfigurationOfPharoLauncher. Am I doing something wrong ?
Notice at [1] that its upstream trigger is [2] which has no upstream project, and all builds have been started by Damien by hand (hover over the person icons). I guess the approach is that uploads to the PharoLauncher repository can be fairly unrestricted, with only the risk only of breaking [3] as the bleeding edge CI job (also trigger by Pharo bleeding edge updates). I like this approach since it helps collaboration and review of changes, with less fear uploading a change will break the world, with more quality control applied to [1] as a "Release" mechanism. [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/ [2] https://ci.inria.fr/pharo-contribution/job/ PharoLauncherFinalUserImage/ [3] https://ci.inria.fr/pharo-contribution/job/PharoLauncher/
cheers -ben
On Wed, Sep 10, 2014 at 11:36 AM, kilon alios <kilon.alios@gmail.com> wrote:
ah ok yes I realised that it was a complex process one build triggering the other build but I did not notice it was triggered manually. Yes I agree thats a good idea but I expected this control to be at Configuration level by having a "stable" release.
Ben explanation is the way I'm doing it currently. Your way is the way I would like it to be :-). But I had no time to give to any Smalltalk development recently. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
I could do it, if you want me to include specific version from packages . Or if you want some versioning scheme. For example what version you want this stable release to be ? We keep the bleeding edge for latest stuff like my progress bar and as soon as things work without problem we integrate them into the next version ? You have any guidelines you want me to follow ? On Wed, Sep 10, 2014 at 5:56 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Sep 10, 2014 at 11:36 AM, kilon alios <kilon.alios@gmail.com> wrote:
ah ok yes I realised that it was a complex process one build triggering the other build but I did not notice it was triggered manually. Yes I agree thats a good idea but I expected this control to be at Configuration level by having a "stable" release.
Ben explanation is the way I'm doing it currently. Your way is the way I would like it to be :-). But I had no time to give to any Smalltalk development recently.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios@gmail.com> wrote:
I could do it, if you want me to include specific version from packages . Or if you want some versioning scheme. For example what version you want this stable release to be ?
0.2.0 (totally random). I'm waiting for input from the Pharo board before releasing 1.0.
We keep the bleeding edge for latest stuff like my progress bar and as soon as things work without problem we integrate them into the next version ?
yes
You have any guidelines you want me to follow ?
use the workflow of versionner. Thank you Kilon -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
will do, my pleasure On Wed, Sep 10, 2014 at 7:30 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios@gmail.com> wrote:
I could do it, if you want me to include specific version from packages . Or if you want some versioning scheme. For example what version you want this stable release to be ?
0.2.0 (totally random). I'm waiting for input from the Pharo board before releasing 1.0.
We keep the bleeding edge for latest stuff like my progress bar and as soon as things work without problem we integrate them into the next version ?
yes
You have any guidelines you want me to follow ?
use the workflow of versionner.
Thank you Kilon
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
participants (3)
-
Ben Coman -
Damien Cassou -
kilon alios