Re: [Pharo-dev] periodic auto actions on bug tracker

2018-12-08 Thread Tim Mackinnon
It’s a great idea - I too have a good look at what I previously reported and decide if it’s still relevant and whether it makes sense to still pursue it. Sent from my iPhone > On 9 Dec 2018, at 06:20, Ben Coman wrote: > > I support the auto-closing of old tickets to avoid bug bankruptcy. Some

[Pharo-dev] Calypso equivalent

2018-12-08 Thread Ben Coman
What is the Calypso equivalent of ? I need to add an extra menu item to the Packages context menu. cheers -ben

[Pharo-dev] Fixed by reboot

2018-12-08 Thread Ben Coman
Just reporting a strange occurrence in case anyone sees the same. I was using PharoLauncher fine, then it wasn't. When trying to launch an image it started reporting with "ProcessWrapper newProcess failed..." First time I've ever seen that, and fixed by a reboot, but still strange. There are a co

[Pharo-dev] periodic auto actions on bug tracker

2018-12-08 Thread Ben Coman
I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. It would be useful to expand this a bit to have a quarterly mail out saying some

Re: [Pharo-dev] Release candidate version numbers

2018-12-08 Thread Ben Coman
> > Le sam. 8 déc. 2018 à 13:42, Ben Coman a écrit : > >> In PharoLauncher >> >> under "Pharo 7 (development version)" opening template >> Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit >> then System > System Report shows... >> >> Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227

Re: [Pharo-dev] Playground "remote publish" feedback from discord

2018-12-08 Thread Ben Coman
On Sun, 9 Dec 2018 at 00:56, Sven Van Caekenberghe wrote: > Ben, > > > On 8 Dec 2018, at 17:19, Ben Coman wrote: > > > > On discord a user provided some feedback... > > > > when you post anything to ws.stfx.eu - e.g. here: > http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use > "ZnW

Re: [Pharo-dev] Release candidate version numbers

2018-12-08 Thread Guillermo Polito
Hi, i think it may come from the fact that this is a new branch (development got renamed into pharo7.0) guille Le sam. 8 déc. 2018 à 13:42, Ben Coman a écrit : > In PharoLauncher > > under "Pharo 7 (development version)" opening template > Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit

Re: [Pharo-dev] Playground "remote publish" feedback from discord

2018-12-08 Thread Sven Van Caekenberghe
Ben, > On 8 Dec 2018, at 17:19, Ben Coman wrote: > > On discord a user provided some feedback... > > when you post anything to ws.stfx.eu - e.g. here: > http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace > openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it.

[Pharo-dev] Release candidate version numbers

2018-12-08 Thread Ben Coman
In PharoLauncher under "Pharo 7 (development version)" opening template Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit then System > System Report shows... Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 Bit) but under "Official distributions" I see

[Pharo-dev] Playground "remote publish" feedback from discord

2018-12-08 Thread Ben Coman
On discord a user provided some feedback... when you post anything to ws.stfx.eu - e.g. here: http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. However, there is no class called "ZnWorkspace" in Pharo 6.1 so th