Smalltalk › Squeak › Squeak VM

Migration to github status?

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 4 messages Options
EstebanLM
Reply | Threaded
Open this post in threaded view
♦
♦
|

Migration to github status?

EstebanLM
 
Hi, 

Last week (with help of Clement) I put online the 64bits image generation for Pharo. 
Our CI now is producing regularly 64bits for both: 


Now… I would like to start testing it, and for that I need to build also PharoVM 64bits… I do not wan to reproduce all the work already done for running 64bits in current  so I’m urging you to complete the migration, so I can start to merge my changes into the master, instead the opposite :)

cheers, 
Esteban
timfelgentreff
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Migration to github status?

timfelgentreff
 

Fabio and I have finished integrating the changes to move to Github with a minimal patch against the current Cog branch. All scripts and build files have been migrated and we are building VMs for Newspeak, Squeak, and Pharo in the available flavor combinations (stack, cog, sista, spur, v3) on (what we think are) the most important platforms (linux, mac, windows) and the most used architectures (x86, x86_64, ARM).

The patch ist currently on github.com/timfel/squeakvm and can be rebased onto the current SVN easily. I have currently disabled uploading the build artifacts. I was thinking maybe we could still use Eliot's webspace or else Bintray, but whatever the community thinks works best.

As soon as everyone is happy with it the patch, we need to find a time when we switch the SVN to read-only and I rebase the patch one last time and then we go live on OpenSmalltalk/vm

Best,
Tim

Am 03.06.2016 15:25 schrieb "Esteban Lorenzano" <[hidden email]>:
 
Hi, 

Last week (with help of Clement) I put online the 64bits image generation for Pharo. 
Our CI now is producing regularly 64bits for both: 


Now… I would like to start testing it, and for that I need to build also PharoVM 64bits… I do not wan to reproduce all the work already done for running 64bits in current  so I’m urging you to complete the migration, so I can start to merge my changes into the master, instead the opposite :)

cheers, 
Esteban
EstebanLM
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Migration to github status?

EstebanLM
 
Hi, 

Sorry for urging on this, but as I said, I need to start working in this… Fabio just told me that he is ready for the migration and this mails from Tim confirmes it… 
Can we schedule the migration?

Let’s say some day next week? (Thursday, as Fabio suggested)?

Can we have a “good to go”?

thanks! 
Esteban

On 07 Jun 2016, at 20:13, Tim Felgentreff <[hidden email]> wrote:

Fabio and I have finished integrating the changes to move to Github with a minimal patch against the current Cog branch. All scripts and build files have been migrated and we are building VMs for Newspeak, Squeak, and Pharo in the available flavor combinations (stack, cog, sista, spur, v3) on (what we think are) the most important platforms (linux, mac, windows) and the most used architectures (x86, x86_64, ARM).

The patch ist currently on github.com/timfel/squeakvm and can be rebased onto the current SVN easily. I have currently disabled uploading the build artifacts. I was thinking maybe we could still use Eliot's webspace or else Bintray, but whatever the community thinks works best.

As soon as everyone is happy with it the patch, we need to find a time when we switch the SVN to read-only and I rebase the patch one last time and then we go live on OpenSmalltalk/vm

Best,
Tim

Am 03.06.2016 15:25 schrieb "Esteban Lorenzano" <[hidden email]>:
 
Hi, 

Last week (with help of Clement) I put online the 64bits image generation for Pharo. 
Our CI now is producing regularly 64bits for both: 


Now… I would like to start testing it, and for that I need to build also PharoVM 64bits… I do not wan to reproduce all the work already done for running 64bits in current  so I’m urging you to complete the migration, so I can start to merge my changes into the master, instead the opposite :)

cheers, 
Esteban
timfelgentreff
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Migration to github status?

timfelgentreff
 

Hi Esteban,

Eliot is looking at the patch for moving to Github, if he thinks its alright, we can switch over pretty much immediately.

cheers,
Tim

Am 10.06.2016 3:01 nachm. schrieb "Esteban Lorenzano" <[hidden email]>:
 
Hi, 

Sorry for urging on this, but as I said, I need to start working in this… Fabio just told me that he is ready for the migration and this mails from Tim confirmes it… 
Can we schedule the migration?

Let’s say some day next week? (Thursday, as Fabio suggested)?

Can we have a “good to go”?

thanks! 
Esteban

On 07 Jun 2016, at 20:13, Tim Felgentreff <[hidden email]> wrote:

Fabio and I have finished integrating the changes to move to Github with a minimal patch against the current Cog branch. All scripts and build files have been migrated and we are building VMs for Newspeak, Squeak, and Pharo in the available flavor combinations (stack, cog, sista, spur, v3) on (what we think are) the most important platforms (linux, mac, windows) and the most used architectures (x86, x86_64, ARM).

The patch ist currently on github.com/timfel/squeakvm and can be rebased onto the current SVN easily. I have currently disabled uploading the build artifacts. I was thinking maybe we could still use Eliot's webspace or else Bintray, but whatever the community thinks works best.

As soon as everyone is happy with it the patch, we need to find a time when we switch the SVN to read-only and I rebase the patch one last time and then we go live on OpenSmalltalk/vm

Best,
Tim

Am 03.06.2016 15:25 schrieb "Esteban Lorenzano" <[hidden email]>:
 
Hi, 

Last week (with help of Clement) I put online the 64bits image generation for Pharo. 
Our CI now is producing regularly 64bits for both: 


Now… I would like to start testing it, and for that I need to build also PharoVM 64bits… I do not wan to reproduce all the work already done for running 64bits in current  so I’m urging you to complete the migration, so I can start to merge my changes into the master, instead the opposite :)

cheers, 
Esteban
Free forum by Nabble Edit this page