Pharo 6 update catalog entries

> Hi,
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
> - load them into Pharo 6 to see if they could be loaded cleanly
>    (due to automatic transformation of deprecated messages your packages
>     get dirty when converted)
>  - check if they are already/still working in Pharo 6 by using them
>  - check that the tests are running in Pharo 6
>  - check that we have a proper config with catalog methods and
>    that the latest config is in the MetaRepoForPharo60 repository
>    http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60
> I did a pass over most projects I implemented or contributed to
> and we now have much more Pharo 6 based projects in catalog:
> - Units, Artefact
>  - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile
>  - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser
>  - ScriptManager (now with icons)
>  - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz
>  - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian
>  - ...
> You should do the same with your projects!
> Also if you have a project on SqueakSource, STHub or GitHub that
> is not yet in the catalog it would be good to provide a  
> ConfigurationOf...
> with a catalog description. Using Versionner it is easy to create one
> or generate the required catalog methods.
> This would give more visibility to your projects!
> Thanks
> T.

> Hi,
>
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
>
>  - load them into Pharo 6 to see if they could be loaded cleanly
>    (due to automatic transformation of deprecated messages your packages
>     get dirty when converted)
>  - check if they are already/still working in Pharo 6 by using them
>  - check that the tests are running in Pharo 6
>  - check that we have a proper config with catalog methods and
>    that the latest config is in the MetaRepoForPharo60 repository
>    http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60
>
> I did a pass over most projects I implemented or contributed to
> and we now have much more Pharo 6 based projects in catalog:
>
>  - Units, Artefact
>  - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile
>  - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser
>  - ScriptManager (now with icons)
>  - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz
>  - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian
>  - ...
>
> You should do the same with your projects!
>
> Also if you have a project on SqueakSource, STHub or GitHub that
> is not yet in the catalog it would be good to provide a ConfigurationOf...
> with a catalog description. Using Versionner it is easy to create one
> or generate the required catalog methods.
>
> This would give more visibility to your projects!
>
> Thanks
> T.
>

> On 31 Jan 2017, at 10:44, Torsten Bergmann <[hidden email]> wrote:
>
> Hi,
>
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
>
> - load them into Pharo 6 to see if they could be loaded cleanly
>   (due to automatic transformation of deprecated messages your packages
>    get dirty when converted)
> - check if they are already/still working in Pharo 6 by using them
> - check that the tests are running in Pharo 6
> - check that we have a proper config with catalog methods and
>   that the latest config is in the MetaRepoForPharo60 repository
>   http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60
>
> I did a pass over most projects I implemented or contributed to
> and we now have much more Pharo 6 based projects in catalog:
>
> - Units, Artefact
> - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile
> - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser
> - ScriptManager (now with icons)
> - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz
> - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian
> - ...
>
> You should do the same with your projects!
>
> Also if you have a project on SqueakSource, STHub or GitHub that
> is not yet in the catalog it would be good to provide a ConfigurationOf...
> with a catalog description. Using Versionner it is easy to create one
> or generate the required catalog methods.
>
> This would give more visibility to your projects!
>
> Thanks
> T.
>

> On 3 Feb 2017, at 13:36, Cyril Ferlicot D. <[hidden email]> wrote:
>
> On 02/02/2017 17:18, Sven Van Caekenberghe wrote:
>> Good idea, Torsten!
>>
>> I updated the following (with new #stable releases and catalog configs for Pharo 3,4,5 & 6):
>>
>> - NeoCSV
>> - NeoJSON
>> - Ston
>> - ZTimestamp
>> - Stamp
>> - ZincHTTPComponents
>> - Zodiac
>> - WebSockets
>> - Zinc SSO
>>
>> These were already running 6.0 builds on the CI servers.
>>
>> Sven
>>
>>
>
> Hi Sven,
>
> There is an error for the ZincHTTPComponents one in
> ConfigurationOfZincHTTPComponents>>#version281:
>
> `package: 'Zinc-Seaside' with: 'Zinc-Seaside-JohanBrichau.46'`
>
> should be
>
> `package: 'Zinc-Seaside' with: 'Zinc-Seaside-SvenVanCaekenberghe.46'`
>
>
> It breaks Seaside of Pharo 5-6.
>
> Thank you for the updates!
>
> --
> Cyril Ferlicot
>
> http://www.synectique.eu
>
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France