Esteban’s list of blocking issues for release Pharo 6.0 (updated to April 10)

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

Esteban’s list of blocking issues for release Pharo 6.0 (updated to April 10)

EstebanLM
Hello,

This are the pending issues for release Pharo 6.0:

VM:
===
- NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed.
- make all tests pass (there are still some failing tests when compiling a new VM).
- libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didn’t had the time to test it.

Image:
=====
- iceberg hit the image

Fixed last week:
---------------------

- win32, cairo fonts problem
- leak revision by Pavel
(and of course several issues not mentioned in the list).

Next:
- Make the release!
- Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :)

By the way… this is a list we have to accomplish in order to make a release (so you know our pain):

- Prepare release notes
Image:
- add welcome browser
- generate PharoV60.sources
- move SystemVersion
- prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P)
VM:
- stable for 6.0 release
WebSite:
- Update index
- Update download page
Infrastructure:
- ZeroConf: Open new 7.0 development
- SmalltalkCI: Open new 7.0 development
- Create platform stable versions
- Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still)
- And talking about travis: prepare all new process on github/travis/appveyor
Pub:
- announce post
- announce mail
- post to YC, Reddit

… and I’m sure I’m forgetting a lot more I will remember in the process of making the release.

(which is one of the reasons why we do not have “more releases in a year”)

Anyway, do not despair… we are almost there!

cheers!
Esteban



Reply | Threaded
Open this post in threaded view
|

Re: Esteban’s list of blocking issues for release Pharo 6.0 (updated to April 10)

Aliaksei Syrel
Hi Esteban,

Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window)
I am just curious :)

Cheers,
Alex

On 10 April 2017 at 09:20, Esteban Lorenzano <[hidden email]> wrote:
Hello,

This are the pending issues for release Pharo 6.0:

VM:
===
- NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed.
- make all tests pass (there are still some failing tests when compiling a new VM).
- libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didn’t had the time to test it.

Image:
=====
- iceberg hit the image

Fixed last week:
---------------------

- win32, cairo fonts problem
- leak revision by Pavel
(and of course several issues not mentioned in the list).

Next:
- Make the release!
- Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :)

By the way… this is a list we have to accomplish in order to make a release (so you know our pain):

- Prepare release notes
Image:
- add welcome browser
- generate PharoV60.sources
- move SystemVersion
- prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P)
VM:
- stable for 6.0 release
WebSite:
- Update index
- Update download page
Infrastructure:
- ZeroConf: Open new 7.0 development
- SmalltalkCI: Open new 7.0 development
- Create platform stable versions
- Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still)
- And talking about travis: prepare all new process on github/travis/appveyor
Pub:
- announce post
- announce mail
- post to YC, Reddit

… and I’m sure I’m forgetting a lot more I will remember in the process of making the release.

(which is one of the reasons why we do not have “more releases in a year”)

Anyway, do not despair… we are almost there!

cheers!
Esteban




Reply | Threaded
Open this post in threaded view
|

Re: Esteban’s list of blocking issues for release Pharo 6.0 (updated to April 10)

EstebanLM

On 10 Apr 2017, at 11:39, Aliaksei Syrel <[hidden email]> wrote:

Hi Esteban,

Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window)
I am just curious :)

Sorry, no. 
Last time that was made by replacing the complete Cocoa backend (from OpenGL to CoreGraphics). 
While that can be done, it is not realist it will arrive for Pharo 6.0 at all. 

Esteban


Cheers,
Alex

On 10 April 2017 at 09:20, Esteban Lorenzano <[hidden email]> wrote:
Hello,

This are the pending issues for release Pharo 6.0:

VM:
===
- NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed.
- make all tests pass (there are still some failing tests when compiling a new VM).
- libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didn’t had the time to test it.

Image:
=====
- iceberg hit the image

Fixed last week:
---------------------

- win32, cairo fonts problem
- leak revision by Pavel
(and of course several issues not mentioned in the list).

Next:
- Make the release!
- Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :)

By the way… this is a list we have to accomplish in order to make a release (so you know our pain):

- Prepare release notes
Image:
- add welcome browser
- generate PharoV60.sources
- move SystemVersion
- prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P)
VM:
- stable for 6.0 release
WebSite:
- Update index
- Update download page
Infrastructure:
- ZeroConf: Open new 7.0 development
- SmalltalkCI: Open new 7.0 development
- Create platform stable versions
- Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still)
- And talking about travis: prepare all new process on github/travis/appveyor
Pub:
- announce post
- announce mail
- post to YC, Reddit

… and I’m sure I’m forgetting a lot more I will remember in the process of making the release.

(which is one of the reasons why we do not have “more releases in a year”)

Anyway, do not despair… we are almost there!

cheers!
Esteban