Re: [Pharo-dev] [Ann] New version of Mocketry 3.0

Hello guys, a feature idea/request… This weekend I was binge-watching talks from Ruby conferences, by Sandi Metz and Katrina Owen on OO design, refactoring, and testing. Highly recommended, and at least Sandi is an experienced smalltalker. See for instance RailsConf 2016 - Succession by Katrina

[Pharo-dev] [pharo-project/pharo-core] 82761e: 60081

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 82761ef6bfad01425d3d28814dd7b72a4395c1e3 https://github.com/pharo-project/pharo-core/commit/82761ef6bfad01425d3d28814dd7b72a4395c1e3 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60081 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] IMPORTANT: Proposal to create a github team for Voyage and MongoTalk

On Fri, Jun 10, 2016 at 08:18:51AM -0700, Todd Blanchard wrote: > 'NoSQL' covers a lot of ground. Excerpted from an old blog post of mine: Riak: - Runar Jordahl's [EpigentRiakInterface](http://squeaksource.com/EpigentRiakInterface). - Goran Krampe's fork,

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60080 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 9ce64d: 60080

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9ce64d0d95207eeef83586fa91e37b792ef74606 https://github.com/pharo-project/pharo-core/commit/9ce64d0d95207eeef83586fa91e37b792ef74606 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core] a72a72: 60079

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a72a728f22884bd1aab16e1ffa5b21a151dde715 https://github.com/pharo-project/pharo-core/commit/a72a728f22884bd1aab16e1ffa5b21a151dde715 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60079 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] A question on the catalog

We will sit down with Pavel. I was thinking that we should have a process like this one: Inbox50 -> validated for current version -> pushed into distribution 50 -> not validated -> moved into currently not working for distribution 50