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
a
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
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
wrote:
>
> On 18 Feb 2015, at 16:34, Esteban Lorenzano wrote:
>
> one less :)
> but really, the problem is that those issu
> On 18 Feb 2015, at 16:34, Esteban Lorenzano 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
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-leve
2015-02-18 15:46 GMT+01:00 Esteban Lorenzano :
> 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*, w
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 wrote:
>
> What is the state of OSWindow inte
What is the state of OSWindow integration?
This release or later?
2015-02-18 13:28 GMT+01:00 Esteban Lorenzano :
> 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 A
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
