Code Freeze 1.1?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

Code Freeze 1.1?

Marcus Denker-4
Hi,

Now with 1.0 done, I think we should think about freezing 1.1.

The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
thing is that 1.1 did change quite some things that have impact on external code (Preferences,
as an example).

So I think we should
       
        -> start slowing down on 1.1 (Stef suggested that already)
        -> start polishing   (tests...)
        -> start to look at the Dev image.
        -> Official code freeze end of March.
        -> Release if possible end of April (this of course depends on the state of things).


Any reasons against?


        Marcus


--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Tudor Girba
Hi,

Is 1.0 already released?

Cheers,
Doru


On 16 Mar 2010, at 10:19, Marcus Denker wrote:

> Hi,
>
> Now with 1.0 done, I think we should think about freezing 1.1.
>
> The main reason of course is that 1.1 is *far more pleasent* to use  
> than 1.0. The other
> thing is that 1.1 did change quite some things that have impact on  
> external code (Preferences,
> as an example).
>
> So I think we should
>
> -> start slowing down on 1.1 (Stef suggested that already)
> -> start polishing   (tests...)
> -> start to look at the Dev image.
> -> Official code freeze end of March.
> -> Release if possible end of April (this of course depends on the  
> state of things).
>
>
> Any reasons against?
>
>
> Marcus
>
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"Some battles are better lost than fought."



--
www.tudorgirba.com

"From an abstract enough point of view, any two things are similar."




_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Marcus Denker-4

On Mar 16, 2010, at 10:40 AM, Tudor Girba wrote:

> Hi,
>
> Is 1.0 already released?
>
Not yet, but we hope that RC3 is the last...

        Marcus



> Cheers,
> Doru
>
>
> On 16 Mar 2010, at 10:19, Marcus Denker wrote:
>
>> Hi,
>>
>> Now with 1.0 done, I think we should think about freezing 1.1.
>>
>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
>> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
>> as an example).
>>
>> So I think we should
>>
>> -> start slowing down on 1.1 (Stef suggested that already)
>> -> start polishing   (tests...)
>> -> start to look at the Dev image.
>> -> Official code freeze end of March.
>> -> Release if possible end of April (this of course depends on the state of things).
>>
>>
>> Any reasons against?
>>
>>
>> Marcus
>>
>>
>> --
>> Marcus Denker  -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> www.tudorgirba.com
>
> "Some battles are better lost than fought."
>
>
>
> --
> www.tudorgirba.com
>
> "From an abstract enough point of view, any two things are similar."
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Tudor Girba
I do not see it from the website. Where can I get it from?

Cheers,
Doru


On 16 Mar 2010, at 10:42, Marcus Denker wrote:

>
> On Mar 16, 2010, at 10:40 AM, Tudor Girba wrote:
>
>> Hi,
>>
>> Is 1.0 already released?
>>
> Not yet, but we hope that RC3 is the last...
>
> Marcus
>
>
>
>> Cheers,
>> Doru
>>
>>
>> On 16 Mar 2010, at 10:19, Marcus Denker wrote:
>>
>>> Hi,
>>>
>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>
>>> The main reason of course is that 1.1 is *far more pleasent* to  
>>> use than 1.0. The other
>>> thing is that 1.1 did change quite some things that have impact on  
>>> external code (Preferences,
>>> as an example).
>>>
>>> So I think we should
>>>
>>> -> start slowing down on 1.1 (Stef suggested that already)
>>> -> start polishing   (tests...)
>>> -> start to look at the Dev image.
>>> -> Official code freeze end of March.
>>> -> Release if possible end of April (this of course depends on  
>>> the state of things).
>>>
>>>
>>> Any reasons against?
>>>
>>>
>>> Marcus
>>>
>>>
>>> --
>>> Marcus Denker  -- http://www.marcusdenker.de
>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> www.tudorgirba.com
>>
>> "Some battles are better lost than fought."
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "From an abstract enough point of view, any two things are similar."
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"The coherence of a trip is given by the clearness of the goal."





_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Lukas Renggli
https://gforge.inria.fr/frs/download.php/26668/PharoCore-1.0-10515rc3.zip

On 16 March 2010 11:53, Tudor Girba <[hidden email]> wrote:

> I do not see it from the website. Where can I get it from?
>
> Cheers,
> Doru
>
>
> On 16 Mar 2010, at 10:42, Marcus Denker wrote:
>
>>
>> On Mar 16, 2010, at 10:40 AM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> Is 1.0 already released?
>>>
>> Not yet, but we hope that RC3 is the last...
>>
>>        Marcus
>>
>>
>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 16 Mar 2010, at 10:19, Marcus Denker wrote:
>>>
>>>> Hi,
>>>>
>>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>>
>>>> The main reason of course is that 1.1 is *far more pleasent* to use than
>>>> 1.0. The other
>>>> thing is that 1.1 did change quite some things that have impact on
>>>> external code (Preferences,
>>>> as an example).
>>>>
>>>> So I think we should
>>>>
>>>>        -> start slowing down on 1.1 (Stef suggested that already)
>>>>        -> start polishing   (tests...)
>>>>        -> start to look at the Dev image.
>>>>        -> Official code freeze end of March.
>>>>        -> Release if possible end of April (this of course depends on
>>>> the state of things).
>>>>
>>>>
>>>> Any reasons against?
>>>>
>>>>
>>>>        Marcus
>>>>
>>>>
>>>> --
>>>> Marcus Denker  -- http://www.marcusdenker.de
>>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Some battles are better lost than fought."
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "From an abstract enough point of view, any two things are similar."
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> Marcus Denker  -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> www.tudorgirba.com
>
> "The coherence of a trip is given by the clearness of the goal."
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Alexandre Bergel
In reply to this post by Tudor Girba
>>>   https://gforge.inria.fr/frs/download.php/26668/PharoCore-1.0-10515rc3.zip

Alexandre


On 16 Mar 2010, at 06:53, Tudor Girba wrote:

> I do not see it from the website. Where can I get it from?
>
> Cheers,
> Doru
>
>
> On 16 Mar 2010, at 10:42, Marcus Denker wrote:
>
>>
>> On Mar 16, 2010, at 10:40 AM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> Is 1.0 already released?
>>>
>> Not yet, but we hope that RC3 is the last...
>>
>> Marcus
>>
>>
>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 16 Mar 2010, at 10:19, Marcus Denker wrote:
>>>
>>>> Hi,
>>>>
>>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>>
>>>> The main reason of course is that 1.1 is *far more pleasent* to  
>>>> use than 1.0. The other
>>>> thing is that 1.1 did change quite some things that have impact  
>>>> on external code (Preferences,
>>>> as an example).
>>>>
>>>> So I think we should
>>>>
>>>> -> start slowing down on 1.1 (Stef suggested that already)
>>>> -> start polishing   (tests...)
>>>> -> start to look at the Dev image.
>>>> -> Official code freeze end of March.
>>>> -> Release if possible end of April (this of course depends on  
>>>> the state of things).
>>>>
>>>>
>>>> Any reasons against?
>>>>
>>>>
>>>> Marcus
>>>>
>>>>
>>>> --
>>>> Marcus Denker  -- http://www.marcusdenker.de
>>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Some battles are better lost than fought."
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "From an abstract enough point of view, any two things are similar."
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> Marcus Denker  -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> www.tudorgirba.com
>
> "The coherence of a trip is given by the clearness of the goal."
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
In reply to this post by Marcus Denker-4
+ 1
end of march for a code freeze would be great.
Stef


On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:

> Hi,
>
> Now with 1.0 done, I think we should think about freezing 1.1.
>
> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
> as an example).
>
> So I think we should
>
> -> start slowing down on 1.1 (Stef suggested that already)
> -> start polishing   (tests...)
> -> start to look at the Dev image.
> -> Official code freeze end of March.
> -> Release if possible end of April (this of course depends on the state of things).
>
>
> Any reasons against?
>
>
> Marcus
>
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Alexandre Bergel
Moose, including Mondrian and Spy load well in Pharo 1.1. No big  
effort were needed for this.
I haven't seen that many problems in porting applications to 1.1.

The only thing I bumped into so far, are initialExtent (but apparently  
this was fixed) and tool registration.

Alexandre


On 16 Mar 2010, at 07:50, Stéphane Ducasse wrote:

> + 1
> end of march for a code freeze would be great.
> Stef
>
>
> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
>
>> Hi,
>>
>> Now with 1.0 done, I think we should think about freezing 1.1.
>>
>> The main reason of course is that 1.1 is *far more pleasent* to use  
>> than 1.0. The other
>> thing is that 1.1 did change quite some things that have impact on  
>> external code (Preferences,
>> as an example).
>>
>> So I think we should
>>
>> -> start slowing down on 1.1 (Stef suggested that already)
>> -> start polishing   (tests...)
>> -> start to look at the Dev image.
>> -> Official code freeze end of March.
>> -> Release if possible end of April (this of course depends on the  
>> state of things).
>>
>>
>> Any reasons against?
>>
>>
>> Marcus
>>
>>
>> --
>> Marcus Denker  -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Henrik Sperre Johansen
Trying to load Magma after the announcement yesterday, I ran into issues with 4 causes:

- Flaps removal
- MethodProperties removal
- Underscore assignement
- Network :P

Obviously, the tests were hard to run without a network, some of the Collection tests seemed to run excessively long as well (in that I alt-. before they finished).

There's also the Preferences deprecation, which is bound to cause some work.

Cheers,
Henry

On Mar 16, 2010, at 2:10 39PM, Alexandre Bergel wrote:

> Moose, including Mondrian and Spy load well in Pharo 1.1. No big effort were needed for this.
> I haven't seen that many problems in porting applications to 1.1.
>
> The only thing I bumped into so far, are initialExtent (but apparently this was fixed) and tool registration.
>
> Alexandre
>
>
> On 16 Mar 2010, at 07:50, Stéphane Ducasse wrote:
>
>> + 1
>> end of march for a code freeze would be great.
>> Stef
>>
>>
>> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
>>
>>> Hi,
>>>
>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>
>>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
>>> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
>>> as an example).
>>>
>>> So I think we should
>>>
>>> -> start slowing down on 1.1 (Stef suggested that already)
>>> -> start polishing   (tests...)
>>> -> start to look at the Dev image.
>>> -> Official code freeze end of March.
>>> -> Release if possible end of April (this of course depends on the state of things).
>>>
>>>
>>> Any reasons against?
>>>
>>>
>>> Marcus
>>>
>>>
>>> --
>>> Marcus Denker  -- http://www.marcusdenker.de
>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
Thanks for the feedback

>
> Trying to load Magma after the announcement yesterday, I ran into issues with 4 causes:
>
> - Flaps removal

we got Flaps in 1.0 :)

> - MethodProperties removal
> - Underscore assignement
> - Network :P
>
> Obviously, the tests were hard to run without a network, some of the Collection tests seemed to run excessively long as well (in that I alt-. before they finished).
>
> There's also the Preferences deprecation, which is bound to cause some work.
>
> Cheers,
> Henry
>
> On Mar 16, 2010, at 2:10 39PM, Alexandre Bergel wrote:
>
>> Moose, including Mondrian and Spy load well in Pharo 1.1. No big effort were needed for this.
>> I haven't seen that many problems in porting applications to 1.1.
>>
>> The only thing I bumped into so far, are initialExtent (but apparently this was fixed) and tool registration.
>>
>> Alexandre
>>
>>
>> On 16 Mar 2010, at 07:50, Stéphane Ducasse wrote:
>>
>>> + 1
>>> end of march for a code freeze would be great.
>>> Stef
>>>
>>>
>>> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
>>>
>>>> Hi,
>>>>
>>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>>
>>>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
>>>> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
>>>> as an example).
>>>>
>>>> So I think we should
>>>>
>>>> -> start slowing down on 1.1 (Stef suggested that already)
>>>> -> start polishing   (tests...)
>>>> -> start to look at the Dev image.
>>>> -> Official code freeze end of March.
>>>> -> Release if possible end of April (this of course depends on the state of things).
>>>>
>>>>
>>>> Any reasons against?
>>>>
>>>>
>>>> Marcus
>>>>
>>>>
>>>> --
>>>> Marcus Denker  -- http://www.marcusdenker.de
>>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
In reply to this post by Marcus Denker-4
for code 1.1 I would like to be able to remove Preferences.

Stef
On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:

> Hi,
>
> Now with 1.0 done, I think we should think about freezing 1.1.
>
> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
> as an example).
>
> So I think we should
>
> -> start slowing down on 1.1 (Stef suggested that already)
> -> start polishing   (tests...)
> -> start to look at the Dev image.
> -> Official code freeze end of March.
> -> Release if possible end of April (this of course depends on the state of things).
>
>
> Any reasons against?
>
>
> Marcus
>
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Henrik Sperre Johansen

On Mar 16, 2010, at 4:01 51PM, Stéphane Ducasse wrote:

> for code 1.1 I would like to be able to remove Preferences.
>
> Stef

Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed.
Then, in the future, when someone tries to port an old project with Preferences, we can say "Load it into a 1.1 image and fix it there".
Without the availability of such a middle step, it'd be somewhat of a leap getting the code up to date. (unless you do it offline, but that's not really the smalltalk way, is it?)

Cheers,
Henry

> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
>
>> Hi,
>>
>> Now with 1.0 done, I think we should think about freezing 1.1.
>>
>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
>> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
>> as an example).
>>
>> So I think we should
>>
>> -> start slowing down on 1.1 (Stef suggested that already)
>> -> start polishing   (tests...)
>> -> start to look at the Dev image.
>> -> Official code freeze end of March.
>> -> Release if possible end of April (this of course depends on the state of things).
>>
>>
>> Any reasons against?
>>
>>
>> Marcus
>>
>>
>> --
>> Marcus Denker  -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse

On Mar 16, 2010, at 4:52 PM, Henrik Johansen wrote:

>
> On Mar 16, 2010, at 4:01 51PM, Stéphane Ducasse wrote:
>
>> for code 1.1 I would like to be able to remove Preferences.
>>
>> Stef
>
> Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed.

Sure this is why I did not say removed :)
But nobody in the image should refer to it.


> Then, in the future, when someone tries to port an old project with Preferences, we can say "Load it into a 1.1 image and fix it there".
> Without the availability of such a middle step, it'd be somewhat of a leap getting the code up to date. (unless you do it offline, but that's not really the smalltalk way, is it?)
>
> Cheers,
> Henry
>
>> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
>>
>>> Hi,
>>>
>>> Now with 1.0 done, I think we should think about freezing 1.1.
>>>
>>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other
>>> thing is that 1.1 did change quite some things that have impact on external code (Preferences,
>>> as an example).
>>>
>>> So I think we should
>>>
>>> -> start slowing down on 1.1 (Stef suggested that already)
>>> -> start polishing   (tests...)
>>> -> start to look at the Dev image.
>>> -> Official code freeze end of March.
>>> -> Release if possible end of April (this of course depends on the state of things).
>>>
>>>
>>> Any reasons against?
>>>
>>>
>>> Marcus
>>>
>>>
>>> --
>>> Marcus Denker  -- http://www.marcusdenker.de
>>> INRIA Lille -- Nord Europe. Team RMoD.
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Henrik Sperre Johansen

On Mar 16, 2010, at 4:59 27PM, Stéphane Ducasse wrote:

>
> On Mar 16, 2010, at 4:52 PM, Henrik Johansen wrote:
>
>>
>> On Mar 16, 2010, at 4:01 51PM, Stéphane Ducasse wrote:
>>
>>> for code 1.1 I would like to be able to remove Preferences.
>>>
>>> Stef
>>
>> Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed.
>
> Sure this is why I did not say removed :)
> But nobody in the image should refer to it.

Ah, to me it read like you wanted to remove it completely :)

I thought Alain already recreated all uses in the core image as settings?



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
>>>> for code 1.1 I would like to be able to remove Preferences.
>>>>
>>>> Stef
>>>
>>> Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed.
>>
>> Sure this is why I did not say removed :)
>> But nobody in the image should refer to it.
>
> Ah, to me it read like you wanted to remove it completely :)

No I will as the first action in 1.2 :)

> I thought Alain already recreated all uses in the core image as settings?

Not all we still have Preferences used in the image and some fixes reintroduced references.

Stef
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Damien Cassou
In reply to this post by Marcus Denker-4
On Tue, Mar 16, 2010 at 10:19 AM, Marcus Denker <[hidden email]> wrote:
> Now with 1.0 done, I think we should think about freezing 1.1.

What about getting 1.0 completely done/released/advertised before
thinking about freezing 1.1?

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
this is parallel and orthogonal.
and freezing means less radical changes, stabilization.

Stef

On Mar 17, 2010, at 11:53 AM, Damien Cassou wrote:

> On Tue, Mar 16, 2010 at 10:19 AM, Marcus Denker <[hidden email]> wrote:
>> Now with 1.0 done, I think we should think about freezing 1.1.
>
> What about getting 1.0 completely done/released/advertised before
> thinking about freezing 1.1?
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Damien Cassou
On Wed, Mar 17, 2010 at 1:20 PM, Stéphane Ducasse
<[hidden email]> wrote:
> this is parallel and orthogonal.
> and freezing means less radical changes, stabilization.

The problem I see is that as soon as 1.1 gets frozen, people will move
toward 1.2 to add the cool stuffs and 1.0 will get even less interest
than now (which is already quite low compared to what 1.1 gets). At
some point, we have to do the remaining 2% that close the stuff and
let us move forward.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

Stéphane Ducasse
Yes
but 1.0 should be out any time soon :)
and if we say end of march may be it will be end of april :)

Stef

> <[hidden email]> wrote:
>> this is parallel and orthogonal.
>> and freezing means less radical changes, stabilization.
>
> The problem I see is that as soon as 1.1 gets frozen, people will move
> toward 1.2 to add the cool stuffs and 1.0 will get even less interest
> than now (which is already quite low compared to what 1.1 gets). At
> some point, we have to do the remaining 2% that close the stuff and
> let us move forward.
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Code Freeze 1.1?

csrabak
In reply to this post by Damien Cassou

 +1


Em 17/03/2010 07:53, Damien Cassou < [hidden email] > escreveu:
On Tue, Mar 16, 2010 at 10:19 AM, Marcus Denker  wrote:
> Now with 1.0 done, I think we should think about freezing 1.1.

What about getting 1.0 completely done/released/advertised before
thinking about freezing 1.1?

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project