<br><br><div class="gmail_quote">On Thu, Jul 2, 2009 at 10:39 AM, Keith Hodges <span dir="ltr"><<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Eliot Miranda wrote:<br>
> Hi Keith,<br>
><br>
> On Thu, Jul 2, 2009 at 4:20 AM, Keith Hodges <<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a><br>
</div><div class="im">> <mailto:<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>>> wrote:<br>
><br>
> The existing community development model works fine enough.<br>
><br>
> 1. Submit changes as change sets to mantis.<br>
><br>
> 2. Bob builds and tests the changes in a basic image, a dev image<br>
> and a<br>
> full image<br>
><br>
> While you need your changes, and await the release with your fixes<br>
> integrated into it, you can load them manually from Mantis.<br>
><br>
> 3. When Bob builds the new release he automatically loads changesets<br>
> from mantis, and fills in the MC repositories together with commit<br>
> messages.<br>
><br>
> The result is an image that looks as though it has been managed<br>
> with MC,<br>
> but the work is submitted in changesets that we all prefer.<br>
><br>
> This is an open process, and you can see what is due for inclusion or<br>
> not by querying mantis.<br>
><br>
><br>
</div>> I just went to <a href="http://squeak.org" target="_blank">squeak.org</a> <<a href="http://squeak.org" target="_blank">http://squeak.org</a>> and followed community<br>
<div class="im">> links and I can find no reference to Bob. The things I want to be<br>
> able to see and find easily are<br>
><br>
> 1. sample images<br>
</div>On their way.... see <a href="http://ftp.squeak.org/3.11" target="_blank">ftp.squeak.org/3.11</a> for some initial examples where<br>
bob is building the LPF image<br>
<div class="im">> 2. list of packages loaded in the image<br>
</div>This can be be included in the metafile that accompanies every build.<br>
Images also contain documentation of the bug fixes that have been loaded.<br>
<div class="im">> 3. test results (name of class, number of green, yellow and red tests,<br>
> and if possible the assertion that failed or the error message for<br>
> each yellow and red test).<br>
</div>Sure... the results from TestReporter do that. I am working on it. I did<br>
have some icons that you can add to apache to give you the colors.<br>
<div class="im">> How do I get at this kind of info? If I can't get at this then Bob is<br>
> an abstraction I don't understand and can't trust. If it is<br>
> manifested then it needs to be findable easily from <a href="http://squeak.org" target="_blank">squeak.org</a><br>
</div>> <<a href="http://squeak.org" target="_blank">http://squeak.org</a>>.<br>
This info will be available wherever bob is running, bob is supposed be<br>
runnable in a distributed fashion, some results are being synced up to<br>
<a href="http://ftp.squeak.org" target="_blank">ftp.squeak.org</a> however you can see my bob server at<br>
<a href="ftp://squeak:viewpoints@bob.safeprayer.com/bob/output" target="_blank">ftp://squeak:viewpoints@bob.safeprayer.com/bob/output</a></blockquote><div><br></div><div>Good (ish ;) ). Might I suggest that putting effort into making a proper web interface available (Seaside?) would be effort well spent. The ftp interface is better than nothing but it ain't very friendly even with Mac OS X finder integration.</div>
<div><br></div><div>But good. Thanks.</div><div><br></div><div>Why can't we have links from the front page of <a href="http://squeak.org">squeak.org</a> to a page describing this, even if describing it as a nascent effort? That web approachability is IMO absolutely crucial in its gaining acceptance. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><a href="ftp://squeak:viewpoints@bob.safeprayer.com/bob/output" target="_blank"></a><br>
<font color="#888888"><br>
Keith<br>
<br>
<br>
</font></blockquote></div><br>