Marcus, I somewhat understand the logic of "if we didn't find it before this, it's not a problem now" but that attitude quickly leads to a trap. Part of why I did not find this sooner is that I have been struggling to adapt to metacello. I am not convinced that there is much information on how to use it, but there is certainly a lot of mis-information. The end result is a big hurdle to adopting new images. You are already producing 1.2. The core is at 1.1 RC - that's great! But here in the trenches, there is nothing approximating a dev image beta, and I can't figure out how to build it. Then I need a Seaside-enabled image on top of that. There is very little of value I can do with a release until Seaside is present. There is a growing tsunami of source code that I have to get into an image in order to be able to work. I built that process initially in terms of the web image; they are gone so I built it in terms of the dev image; now I can't even get that. Some stability (tenacity might be a better word) in the production of what is delivered to the user/developer would help me be a more aggressive tester. As it is, I am hacking the build process rather than applying it to reach a point that I can contribute to testing. In the extreme case, I could retreat to use Seaside's pre-made images and ignore the bleeding edge of Pharo, but that is not something I care to do. At a minimum, the unstable download section should contain a link to an "official" page that shows how to build the dev and web configurations. If we can't do that, work on 1.2 is premature. Back to 2476, it is quite possible that rydier's suggestion of removing the true return value will allow it to work. We are testing a new release, or should be. Does that not seem like a good time to introduce such a simple fix? Bill ________________________________________ From: pharo@googlecode.com [pharo@googlecode.com] Sent: Saturday, June 12, 2010 3:01 AM To: Schwab,Wilhelm K Subject: Re: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta Updates: Labels: -Milestone-1.1 Comment #6 on issue 2476 by marcus.denker: ConnectionQueue broken in 1.0 and 1.1 beta http://code.google.com/p/pharo/issues/detail?id=2476 In Pharo-dev 1.0 and 1.1 beta: not a show stopper for 1.1 -- You received this message because you are the owner of the issue. You may adjust your issue notification preferences at: https://code.google.com/hosting/settings