Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know? It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that. Marcus -- Marcus Denker -- http://marcusdenker.de
Hi.Tomorow the Hungarian Pharo Bug Hunter Commando will be into action :DI will be test the Pharo 1.3 OneClick on Win32 (XP Pro SP3) and Linux (Debian 6.0) platform with the latest Cog VM and the Squeak Vm. Best Regards Comrades Laszlo Zsolt Kiss
Thanks we like LPBHC Stef On Aug 31, 2011, at 9:06 PM, Laszlo Zsolt Kiss wrote:
Hi. Tomorow the Hungarian Pharo Bug Hunter Commando will be into action. :D I will be test the Pharo 1.3 OneClick on Win32 (XP Pro SP3) and Linux (Debian 6.0) platform with the latest Cog VM and the Squeak Vm.
Best Regards Comrades
Laszlo Zsolt Kiss
Marcus We only do what is possible :) - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded. - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress. So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us. Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
For development configuration is useless and just time sink. But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations. Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another. On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
    - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that.     Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
    - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3.     Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
   Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink. if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are  talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
    - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that.     Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
    - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3.     Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
   Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
On 31 August 2011 23:23, Igor Stasenko <siguctua@gmail.com> wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
unless there is an automated tool which can generate new configuration automatically, hidden in your sleeve .. :)
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are  talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
    - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that.     Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
    - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3.     Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
   Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
unless there is an automated tool which can generate new configuration automatically, hidden in your sleeve .. :)
there is a metacello browser that do that for you. Now I do not know if it handles subproject. The browser supports the process and use the MetacelloToolbox API. I should have a look when I will redo a complete pass on the metacello chapter. I wrote a memento so that we do not have to learn 35 pages to get all the details, but one page with the essential. Stef
On 31 August 2011 23:28, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
unless there is an automated tool which can generate new configuration automatically, hidden in your sleeve .. :)
there is a metacello browser that do that for you. Now I do not know if it handles subproject. The browser supports the process and use the MetacelloToolbox API.
I should have a look when I will redo a complete pass on the metacello chapter.
I wrote a memento so that we do not have to learn 35 pages to get all the details, but one page with the essential.
i need it. because manually updating configs is pain in the ass, and more than that is is error prone.
Stef
-- Best regards, Igor Stasenko AKA sig.
:-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually. Cheers, Alexandre On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
(+1) looks really cool :) Is this already integrated in 1.4? I'm so used to use Monticello browser, but I'd like to give VersionnerBrowser a try :D On 31 August 2011 17:46, Alexandre Bergel <alexandre.bergel@me.com> wrote:
:-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually.
Cheers, Alexandre
On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to
identify what exactly and what version of it will be put in final
version. And gives a simple and concrete answer how to reproduce it,
in case of need.
Since we're are talking about release, i don't see how we could do
that without configurations.
Yes, sure it could be done manually to manifest all packages and their
version(s) included into release, but it still means that
someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that.
Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3.
Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it.
And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some
critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated,
it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be
included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3>
yet?
No... I have not yet found the energy to do that.
Marcus
--
Marcus Denker -- http://marcusdenker.de
--
Best regards,
Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
is it just me, or there are more people who know nothing about it? i know how to do a parallel programs, but i have no means to know what happens in parallel to my little universe unless i can read it from some well known source :) On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> wrote:
:-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually.
Cheers, Alexandre
On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to
identify what exactly and what version of it will be put in final
version. And gives a simple and concrete answer how to reproduce it,
in case of need.
Since we're are talking about release, i don't see how we could do
that without configurations.
Yes, sure it could be done manually to manifest all packages and their
version(s) included into release, but it still means that
someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that.
Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3.
Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it.
And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some
critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated,
it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be
included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3>
yet?
No... I have not yet found the energy to do that.
Marcus
--
Marcus Denker -- http://marcusdenker.de
--
Best regards,
Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
Dale and I worked on the MetacelloBrowser. I believe the UI needs to be polished. Probably having something based on Glamour would cool to have. I worked on Versionner because I just need a commit button. Cheers, Alexandre On 31 Aug 2011, at 17:57, Igor Stasenko wrote:
is it just me, or there are more people who know nothing about it?
i know how to do a parallel programs, but i have no means to know what happens in parallel to my little universe unless i can read it from some well known source :)
On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> wrote: :-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually.
<Screen Shot 2011-08-31 at 17.24.53.png>
Cheers, Alexandre
On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi, For development involving multiple people in the same time, you cannot rely on hardcoded package versions in configurations, because there is no merge support, so you will never know when you are missing a version. The only model that works reliably now is to depend on a baseline for development. That means that when you develop, you integrate relentlessly the latest package versions. When you release you can use the same baseline and hardcode the package versions. Cheers, Doru On 31 Aug 2011, at 23:02, Alexandre Bergel wrote:
Dale and I worked on the MetacelloBrowser. I believe the UI needs to be polished. Probably having something based on Glamour would cool to have. I worked on Versionner because I just need a commit button.
Cheers, Alexandre
On 31 Aug 2011, at 17:57, Igor Stasenko wrote:
is it just me, or there are more people who know nothing about it?
i know how to do a parallel programs, but i have no means to know what happens in parallel to my little universe unless i can read it from some well known source :)
On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> wrote: :-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually.
<Screen Shot 2011-08-31 at 17.24.53.png>
Cheers, Alexandre
On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com "Value is always contextual."
I have longer term plans to support merging...but no support right now... Dale ----- Original Message ----- | From: "Tudor Girba" <tudor@tudorgirba.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, August 31, 2011 3:26:50 PM | Subject: Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release | | Hi, | | For development involving multiple people in the same time, you | cannot rely on hardcoded package versions in configurations, because | there is no merge support, so you will never know when you are | missing a version. | | The only model that works reliably now is to depend on a baseline for | development. That means that when you develop, you integrate | relentlessly the latest package versions. | | When you release you can use the same baseline and hardcode the | package versions. | | Cheers, | Doru | | | On 31 Aug 2011, at 23:02, Alexandre Bergel wrote: | | > Dale and I worked on the MetacelloBrowser. I believe the UI needs | > to be polished. Probably having something based on Glamour would | > cool to have. | > I worked on Versionner because I just need a commit button. | > | > Cheers, | > Alexandre | > | > | > On 31 Aug 2011, at 17:57, Igor Stasenko wrote: | > | >> is it just me, or there are more people who know nothing about it? | >> | >> i know how to do a parallel programs, | >> but i have no means to know what happens in parallel to my little | >> universe unless i can read it from some well known source :) | >> | >> On 31 August 2011 23:46, Alexandre Bergel | >> <alexandre.bergel@me.com> wrote: | >> :-) | >> I use Versionner for simple case and the MetacelloBrowser for more | >> complicated stuff. | >> Check at the screenshot. You see, there is a commit button :-) It | >> saves all the dependent packages, create a new version, ask you | >> for the comment, and save the config. I rarely use the Monticello | >> browser actually. | >> | >> <Screen Shot 2011-08-31 at 17.24.53.png> | >> | >> Cheers, | >> Alexandre | >> | >> | >> On 31 Aug 2011, at 17:23, Igor Stasenko wrote: | >> | >>> On 31 August 2011 23:19, Alexandre Bergel | >>> <alexandre.bergel@me.com> wrote: | >>>>> For development configuration is useless and just time sink. | >>>> | >>>> I strongly disagree. Metacello was sold to please users. | >>>> Actually, I use it for me, the developper. I create a new | >>>> version at each commit. It works wonderfully. | >>>> | >>> | >>> sorry, but if during development you need to do 2 commits of 20 | >>> packages , calculate how much time it would take for you to | >>> manuallly update a configuration for each update. | >>> it is time sink. | >>> | >>> if you do that once per day, its okay.. but for every commit . | >>> no. its | >>> is absurd. | >>> | >>>> Alexandre | >>>> | >>>> | >>>>> But for release it has completely different purpose: it helps | >>>>> us to | >>>>> identify what exactly and what version of it will be put in | >>>>> final | >>>>> version. And gives a simple and concrete answer how to | >>>>> reproduce it, | >>>>> in case of need. | >>>>> Since we're are talking about release, i don't see how we | >>>>> could do | >>>>> that without configurations. | >>>>> | >>>>> Yes, sure it could be done manually to manifest all packages | >>>>> and their | >>>>> version(s) included into release, but it still means that | >>>>> someone has to do it one way or another. | >>>>> | >>>>> | >>>>> On 31 August 2011 23:03, Stéphane Ducasse | >>>>> <stephane.ducasse@inria.fr> wrote: | >>>>>> Marcus | >>>>>> | >>>>>> We only do what is possible :) | >>>>>> | >>>>>> - for the configurations of let us take what exist. We | >>>>>> cannot control everything. I do not have the time and | >>>>>> knowledge for that. | >>>>>> Lukas decided that configurations are evil. Ok perfect | >>>>>> now we fix them when we know what should be loaded. | >>>>>> | >>>>>> - Then for example to integrate the broken highlight I | >>>>>> need the code first. I still do not know which slice to | >>>>>> load in 1.3. | >>>>>> Two days ago I spent time on it loading the wrong slice. | >>>>>> So I decided that I will not stress. | >>>>>> | >>>>>> So we will fix that either in 1.3 or in 1.4 as time allows it. | >>>>>> And more more important: no stress we are payed enough to | >>>>>> stress and do stuff that hurts us. | >>>>>> | >>>>>> Stef | >>>>>> | >>>>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: | >>>>>>> | >>>>>>>> The image contains outdated versions of RB and OB that miss | >>>>>>>> some | >>>>>>>> critical fixes. | >>>>>>> | >>>>>>> How can I know? | >>>>>>> | >>>>>>> It is is build using the latest MetaCello config... if the | >>>>>>> config needs to be updated, | >>>>>>> it needs to be updated. It does not happen by itself. | >>>>>>> | >>>>>>>> Also there some proposed fixes don't seem to be | >>>>>>>> included | >>>>>>>> <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> | >>>>>>>> yet? | >>>>>>>> | >>>>>>> No... I have not yet found the energy to do that. | >>>>>>> | >>>>>>> Marcus | >>>>>>> | >>>>>>> -- | >>>>>>> Marcus Denker -- http://marcusdenker.de | >>>>>>> | >>>>>>> | >>>>>> | >>>>>> | >>>>>> | >>>>> | >>>>> | >>>>> | >>>>> -- | >>>>> Best regards, | >>>>> Igor Stasenko AKA sig. | >>>>> | >>>> | >>>> -- | >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | >>>> Alexandre Bergel http://www.bergel.eu | >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | >>>> | >>>> | >>>> | >>>> | >>>> | >>>> | >>>> | >>> | >>> | >>> | >>> -- | >>> Best regards, | >>> Igor Stasenko AKA sig. | >>> | >> | >> -- | >> | >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | >> Alexandre Bergel http://www.bergel.eu | >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | >> | >> | >> | >> | >> | >> | >> | >> | >> -- | >> Best regards, | >> Igor Stasenko AKA sig. | > | > -- | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > Alexandre Bergel http://www.bergel.eu | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | > | > | > | > | > | | -- | www.tudorgirba.com | | "Value is always contextual." | | | | |
I know this, but I haven't bumped into a serious problem, even when multiple people are committing. I am the only to create a new version though. It has always worked as a charm. Alexandre Le 31 août 2011 à 18:26, Tudor Girba <tudor@tudorgirba.com> a écrit :
Hi,
For development involving multiple people in the same time, you cannot rely on hardcoded package versions in configurations, because there is no merge support, so you will never know when you are missing a version.
The only model that works reliably now is to depend on a baseline for development. That means that when you develop, you integrate relentlessly the latest package versions.
When you release you can use the same baseline and hardcode the package versions.
Cheers, Doru
On 31 Aug 2011, at 23:02, Alexandre Bergel wrote:
Dale and I worked on the MetacelloBrowser. I believe the UI needs to be polished. Probably having something based on Glamour would cool to have. I worked on Versionner because I just need a commit button.
Cheers, Alexandre
On 31 Aug 2011, at 17:57, Igor Stasenko wrote:
is it just me, or there are more people who know nothing about it?
i know how to do a parallel programs, but i have no means to know what happens in parallel to my little universe unless i can read it from some well known source :)
On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> wrote: :-) I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually.
<Screen Shot 2011-08-31 at 17.24.53.png>
Cheers, Alexandre
On 31 Aug 2011, at 17:23, Igor Stasenko wrote:
On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel@me.com> wrote:
For development configuration is useless and just time sink.
I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully.
sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink.
if you do that once per day, its okay.. but for every commit . no. its is absurd.
Alexandre
But for release it has completely different purpose: it helps us to identify what exactly and what version of it will be put in final version. And gives a simple and concrete answer how to reproduce it, in case of need. Since we're are talking about release, i don't see how we could do that without configurations.
Yes, sure it could be done manually to manifest all packages and their version(s) included into release, but it still means that someone has to do it one way or another.
On 31 August 2011 23:03, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Marcus
We only do what is possible :)
- for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded.
- Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress.
So we will fix that either in 1.3 or in 1.4 as time allows it. And more more important: no stress we are payed enough to stress and do stuff that hurts us.
Stef
On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote:
The image contains outdated versions of RB and OB that miss some critical fixes.
How can I know?
It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself.
Also there some proposed fixes don't seem to be included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> yet?
No... I have not yet found the energy to do that.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Best regards, Igor Stasenko AKA sig.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com
"Value is always contextual."
There were some Metacello performance issues that popped up when using the MetacelloBrowser, so I was reluctant to publicize the MetacelloBrowser until the issues were resolved. While working on tODE, I isolated and fixed the performance issues, so the next release of Metacello (soonish) will have fixes for the performance issues and then the MetacelloBrowser will be ready to be used ... it does need some GUI polish ... Dale ----- Original Message ----- | From: "Alexandre Bergel" <alexandre.bergel@me.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, August 31, 2011 2:02:55 PM | Subject: Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release | | Dale and I worked on the MetacelloBrowser. I believe the UI needs to | be polished. Probably having something based on Glamour would cool | to have. | I worked on Versionner because I just need a commit button. | | Cheers, | Alexandre | | | On 31 Aug 2011, at 17:57, Igor Stasenko wrote: | | > is it just me, or there are more people who know nothing about it? | > | > i know how to do a parallel programs, | > but i have no means to know what happens in parallel to my little | > universe unless i can read it from some well known source :) | > | > On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> | > wrote: | > :-) | > I use Versionner for simple case and the MetacelloBrowser for more | > complicated stuff. | > Check at the screenshot. You see, there is a commit button :-) It | > saves all the dependent packages, create a new version, ask you | > for the comment, and save the config. I rarely use the Monticello | > browser actually. | > | > <Screen Shot 2011-08-31 at 17.24.53.png> | > | > Cheers, | > Alexandre | > | > | > On 31 Aug 2011, at 17:23, Igor Stasenko wrote: | > | >> On 31 August 2011 23:19, Alexandre Bergel | >> <alexandre.bergel@me.com> wrote: | >>>> For development configuration is useless and just time sink. | >>> | >>> I strongly disagree. Metacello was sold to please users. | >>> Actually, I use it for me, the developper. I create a new | >>> version at each commit. It works wonderfully. | >>> | >> | >> sorry, but if during development you need to do 2 commits of 20 | >> packages , calculate how much time it would take for you to | >> manuallly update a configuration for each update. | >> it is time sink. | >> | >> if you do that once per day, its okay.. but for every commit . no. | >> its | >> is absurd. | >> | >>> Alexandre | >>> | >>> | >>>> But for release it has completely different purpose: it helps us | >>>> to | >>>> identify what exactly and what version of it will be put in | >>>> final | >>>> version. And gives a simple and concrete answer how to reproduce | >>>> it, | >>>> in case of need. | >>>> Since we're are talking about release, i don't see how we could | >>>> do | >>>> that without configurations. | >>>> | >>>> Yes, sure it could be done manually to manifest all packages and | >>>> their | >>>> version(s) included into release, but it still means that | >>>> someone has to do it one way or another. | >>>> | >>>> | >>>> On 31 August 2011 23:03, Stéphane Ducasse | >>>> <stephane.ducasse@inria.fr> wrote: | >>>>> Marcus | >>>>> | >>>>> We only do what is possible :) | >>>>> | >>>>> - for the configurations of let us take what exist. We | >>>>> cannot control everything. I do not have the time and | >>>>> knowledge for that. | >>>>> Lukas decided that configurations are evil. Ok perfect | >>>>> now we fix them when we know what should be loaded. | >>>>> | >>>>> - Then for example to integrate the broken highlight I | >>>>> need the code first. I still do not know which slice to | >>>>> load in 1.3. | >>>>> Two days ago I spent time on it loading the wrong slice. | >>>>> So I decided that I will not stress. | >>>>> | >>>>> So we will fix that either in 1.3 or in 1.4 as time allows it. | >>>>> And more more important: no stress we are payed enough to | >>>>> stress and do stuff that hurts us. | >>>>> | >>>>> Stef | >>>>> | >>>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: | >>>>>> | >>>>>>> The image contains outdated versions of RB and OB that miss | >>>>>>> some | >>>>>>> critical fixes. | >>>>>> | >>>>>> How can I know? | >>>>>> | >>>>>> It is is build using the latest MetaCello config... if the | >>>>>> config needs to be updated, | >>>>>> it needs to be updated. It does not happen by itself. | >>>>>> | >>>>>>> Also there some proposed fixes don't seem to be | >>>>>>> included | >>>>>>> <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> | >>>>>>> yet? | >>>>>>> | >>>>>> No... I have not yet found the energy to do that. | >>>>>> | >>>>>> Marcus | >>>>>> | >>>>>> -- | >>>>>> Marcus Denker -- http://marcusdenker.de | >>>>>> | >>>>>> | >>>>> | >>>>> | >>>>> | >>>> | >>>> | >>>> | >>>> -- | >>>> Best regards, | >>>> Igor Stasenko AKA sig. | >>>> | >>> | >>> -- | >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | >>> Alexandre Bergel http://www.bergel.eu | >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | >>> | >>> | >>> | >>> | >>> | >>> | >>> | >> | >> | >> | >> -- | >> Best regards, | >> Igor Stasenko AKA sig. | >> | > | > -- | > | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > Alexandre Bergel http://www.bergel.eu | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | > | > | > | > | > | > | > | > -- | > Best regards, | > Igor Stasenko AKA sig. | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | | | |
+1 2011/8/31 Dale Henrichs <dhenrich@vmware.com>:
There were some Metacello performance issues that popped up when using the MetacelloBrowser, so I was reluctant to publicize the MetacelloBrowser until the issues were resolved. While working on tODE, I isolated and fixed the performance issues, so the next release of Metacello (soonish) will have fixes for the performance issues and then the MetacelloBrowser will be ready to be used ... it does need some GUI polish ...
Dale
----- Original Message ----- | From: "Alexandre Bergel" <alexandre.bergel@me.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, August 31, 2011 2:02:55 PM | Subject: Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release | | Dale and I worked on the MetacelloBrowser. I believe the UI needs to | be polished. Probably having something based on Glamour would cool | to have. | I worked on Versionner because I just need a commit button. | | Cheers, | Alexandre | | | On 31 Aug 2011, at 17:57, Igor Stasenko wrote: | | > is it just me, or there are more people who know nothing about it? | > | > i know how to do a parallel programs, | > but i have no means to know what happens in parallel to my little | > universe unless i can read it from some well known source :) | > | > On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel@me.com> | > wrote: | > :-) | > I use Versionner for simple case and the MetacelloBrowser for more | > complicated stuff. | > Check at the screenshot. You see, there is a commit button :-) It | > saves all the dependent packages, create a new version, ask you | > for the comment, and save the config. I rarely use the Monticello | > browser actually. | > | > <Screen Shot 2011-08-31 at 17.24.53.png> | > | > Cheers, | > Alexandre | > | > | > On 31 Aug 2011, at 17:23, Igor Stasenko wrote: | > | >> On 31 August 2011 23:19, Alexandre Bergel | >> <alexandre.bergel@me.com> wrote: | >>>> For development configuration is useless and just time sink. | >>> | >>> I strongly disagree. Metacello was sold to please users. | >>> Actually, I use it for me, the developper. I create a new | >>> version at each commit. It works wonderfully. | >>> | >> | >> sorry, but if during development you need to do 2 commits of 20 | >> packages , calculate how much time it would take for you to | >> manuallly update a configuration for each update. | >> it is time sink. | >> | >> if you do that once per day, its okay.. but for every commit . no. | >> its | >> is absurd. | >> | >>> Alexandre | >>> | >>> | >>>> But for release it has completely different purpose: it helps us | >>>> to | >>>> identify what exactly and what version of it will be put in | >>>> final | >>>> version. And gives a simple and concrete answer how to reproduce | >>>> it, | >>>> in case of need. | >>>> Since we're are  talking about release, i don't see how we could | >>>> do | >>>> that without configurations. | >>>> | >>>> Yes, sure it could be done manually to manifest all packages and | >>>> their | >>>> version(s) included into release, but it still means that | >>>> someone has to do it one way or another. | >>>> | >>>> | >>>> On 31 August 2011 23:03, Stéphane Ducasse | >>>> <stephane.ducasse@inria.fr> wrote: | >>>>> Marcus | >>>>> | >>>>> We only do what is possible :) | >>>>> | >>>>>     - for the configurations of let us take what exist. We | >>>>>     cannot control everything. I do not have the time and | >>>>>     knowledge for that. | >>>>>     Lukas decided that configurations are evil. Ok perfect | >>>>>     now we fix them when we know what should be loaded. | >>>>> | >>>>>     - Then for example to integrate the broken highlight I | >>>>>     need the code first. I still do not know which slice to | >>>>>     load in 1.3. | >>>>>     Two days ago I spent time on it loading the wrong slice. | >>>>>     So I decided that I will not stress. | >>>>> | >>>>> So we will fix that either in 1.3 or in 1.4 as time allows it. | >>>>> And more more important: no stress we are payed enough to | >>>>> stress and do stuff that hurts us. | >>>>> | >>>>> Stef | >>>>> | >>>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: | >>>>>> | >>>>>>> The image contains outdated versions of RB and OB that miss | >>>>>>> some | >>>>>>> critical fixes. | >>>>>> | >>>>>> How can I know? | >>>>>> | >>>>>> It is is build using the latest MetaCello config... if the | >>>>>> config needs to be updated, | >>>>>> it needs to be updated. It does not happen by itself. | >>>>>> | >>>>>>> Also there some proposed fixes don't seem to be | >>>>>>> included | >>>>>>> <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> | >>>>>>> yet? | >>>>>>> | >>>>>> No... I have not yet found the energy to do that. | >>>>>> | >>>>>>    Marcus | >>>>>> | >>>>>> -- | >>>>>> Marcus Denker -- http://marcusdenker.de | >>>>>> | >>>>>> | >>>>> | >>>>> | >>>>> | >>>> | >>>> | >>>> | >>>> -- | >>>> Best regards, | >>>> Igor Stasenko AKA sig. | >>>> | >>> | >>> -- | >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | >>> Alexandre Bergel  http://www.bergel.eu | >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | >>> | >>> | >>> | >>> | >>> | >>> | >>> | >> | >> | >> | >> -- | >> Best regards, | >> Igor Stasenko AKA sig. | >> | > | > -- | > | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > Alexandre Bergel  http://www.bergel.eu | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | > | > | > | > | > | > | > | > -- | > Best regards, | > Igor Stasenko AKA sig. | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel  http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | | | |
-- ================================================= Germán S. Arduino <gsa @ arsol.net>  Twitter: garduino Arduino Software & Web Hosting  http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================
2011/8/31 Igor Stasenko <siguctua@gmail.com>
is it just me, or there are more people who know nothing about it?
I never hear about it neither :S Look as a very useful tool ......
participants (9)
-
Alexandre Bergel -
Clara Allende -
Dale Henrichs -
Germán Arduino -
Igor Stasenko -
Laszlo Zsolt Kiss -
Marcus Denker -
Stéphane Ducasse -
Tudor Girba