Smalltalk › Pharo › Pharo Smalltalk Users

[ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

9 messages Options

EstebanLM

[ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

Nicolai Hess

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:

Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

EstebanLM

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

it depends on your definition of “status” :)

first version is integrated

latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,

Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

Nicolai Hess

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:

it depends on your definition of “status” :)

That is easy to define:

definition of "status" = fogbugz status

-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

EstebanLM

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

one less :)

but really, the problem is that those issues are mistaking issues… For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.

2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.

3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine… steps 2 and 3 are really needed, but far from easy.

The only step that we could mark as “done” right now is the first one… steps 2 and 3 are “more or less” worked… there are prototypes but still not realistic estimation of what amount of time will take to actually do it… It is “thought” to be done in Pharo5… we’ll see.

And the problem on integrating some of those changes is that are “one-way-shots”… once done, we cannot go back.

I will mark some of those issues as “on hold” with a clarification.

cheers,

Esteban

On 18 Feb 2015, at 16:12, Nicolai Hess <[hidden email]> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:
it depends on your definition of “status” :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

EstebanLM

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

On 18 Feb 2015, at 16:34, Esteban Lorenzano <[hidden email]> wrote:

one less :)
but really, the problem is that those issues are mistaking issues… For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.
2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.
3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine… steps 2 and 3 are really needed, but far from easy.
The only step that we could mark as “done” right now is the first one… steps 2 and 3 are “more or less” worked… there are prototypes but still not realistic estimation of what amount of time will take to actually do it… It is “thought” to be done in Pharo5… we’ll see.

And the problem on integrating some of those changes is that are “one-way-shots”… once done, we cannot go back.
I will mark some of those issues as “on hold” with a clarification.

done

cheers,
Esteban

On 18 Feb 2015, at 16:12, Nicolai Hess <[hidden email]> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:
it depends on your definition of “status” :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

Ben Coman

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

So the in Fogbugz we need probably milestone tags for Pharo 4.1 and Pharo 5.0 so we can push issues to them.

cheers -ben

On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <[hidden email]> wrote:

On 18 Feb 2015, at 16:34, Esteban Lorenzano <[hidden email]> wrote:

one less :)
but really, the problem is that those issues are mistaking issues… For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.
2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.
3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine… steps 2 and 3 are really needed, but far from easy.
The only step that we could mark as “done” right now is the first one… steps 2 and 3 are “more or less” worked… there are prototypes but still not realistic estimation of what amount of time will take to actually do it… It is “thought” to be done in Pharo5… we’ll see.

And the problem on integrating some of those changes is that are “one-way-shots”… once done, we cannot go back.
I will mark some of those issues as “on hold” with a clarification.

done

cheers,
Esteban

On 18 Feb 2015, at 16:12, Nicolai Hess <[hidden email]> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:
it depends on your definition of “status” :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

Ben Coman

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

So how are externally managed ConfigurationOf packages going to be handled in this period? Last year I felt (maybe unjustified) that more than bug fixes slipped in when an external package like Spec was synchronised in the code freeze period. Do developers of an external package like for Spotter and Playground have to halt their feature development branch, so that bug fixes can be incorporated separately?

cheers -ben

On Thu, Feb 19, 2015 at 12:21 AM, Ben Coman <[hidden email]> wrote:

So the in Fogbugz we need probably milestone tags for Pharo 4.1 and Pharo 5.0 so we can push issues to them.
cheers -ben

On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <[hidden email]> wrote:

On 18 Feb 2015, at 16:34, Esteban Lorenzano <[hidden email]> wrote:

one less :)
but really, the problem is that those issues are mistaking issues… For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.
2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.
3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine… steps 2 and 3 are really needed, but far from easy.
The only step that we could mark as “done” right now is the first one… steps 2 and 3 are “more or less” worked… there are prototypes but still not realistic estimation of what amount of time will take to actually do it… It is “thought” to be done in Pharo5… we’ll see.

And the problem on integrating some of those changes is that are “one-way-shots”… once done, we cannot go back.
I will mark some of those issues as “on hold” with a clarification.

done

cheers,
Esteban

On 18 Feb 2015, at 16:12, Nicolai Hess <[hidden email]> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:
it depends on your definition of “status” :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban

Ben Coman

Re: [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

In reply to this post by EstebanLM

btw, I'd really like to get the following three fixes into Pharo 4 before the code freeze.

* 16 steps to get through #halt
Status: Ready to review (https://pharo.fogbugz.com/default.asp?12970)

* Delay refactoring (part 2b) - clean out newCodeEnabled wrappers
Status: Ready to review (should be easy, https://pharo.fogbugz.com/default.asp?14942)

* Change Delay from milliseconds to microseconds (http://pharo.fogbugz.com/default.asp?14353)

Status: This was reviewed and went for integration a while ago, but needs to be rebased on the build following cleanup of newCodeEnabled (issue 14042).

cheers -ben

On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <[hidden email]> wrote:

On 18 Feb 2015, at 16:34, Esteban Lorenzano <[hidden email]> wrote:

one less :)
but really, the problem is that those issues are mistaking issues… For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.
2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.
3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine… steps 2 and 3 are really needed, but far from easy.
The only step that we could mark as “done” right now is the first one… steps 2 and 3 are “more or less” worked… there are prototypes but still not realistic estimation of what amount of time will take to actually do it… It is “thought” to be done in Pharo5… we’ll see.

And the problem on integrating some of those changes is that are “one-way-shots”… once done, we cannot go back.
I will mark some of those issues as “on hold” with a clarification.

done

cheers,
Esteban

On 18 Feb 2015, at 16:12, Nicolai Hess <[hidden email]> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <[hidden email]>:
it depends on your definition of “status” :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <[hidden email]> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <[hidden email]>:
Hi,

So… I’m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed… we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban