[squeak-dev] A New Community Development Model

The existing community development model works fine enough.

1. Submit changes as change sets to mantis.

2. Bob builds and tests the changes in a basic image, a dev image and a
full image

While you need your changes, and await the release with your fixes
integrated into it, you can load them manually from Mantis.

3. When Bob builds the new release he automatically loads changesets
from mantis, and fills in the MC repositories together with commit messages.

The result is an image that looks as though it has been managed with MC,
but the work is submitted in changesets that we all prefer.

This is an open process, and you can see what is due for inclusion or
not by querying mantis.

Now if certain members of the board would volunteer to contribute to the
process, rather than replacing it without discussion, we would all be a
lot better of.

best regards

Keith

Hi Eliot,

Bob & things are discussed and reported on the release-team list, see for example

- http://lists.squeakfoundation.org/pipermail/release/2009-February/000072.html

/Klaus

On Thu, 02 Jul 2009 19:08:11 +0200, Eliot Miranda wrote:

Hi Keith,

On Thu, Jul 2, 2009 at 4:20 AM, Keith Hodges <[hidden email]>wrote:

The existing community development model works fine enough.

1. Submit changes as change sets to mantis.

2. Bob builds and tests the changes in a basic image, a dev image and a
full image

While you need your changes, and await the release with your fixes
integrated into it, you can load them manually from Mantis.

3. When Bob builds the new release he automatically loads changesets
from mantis, and fills in the MC repositories together with commit
messages.

The result is an image that looks as though it has been managed with MC,
but the work is submitted in changesets that we all prefer.

This is an open process, and you can see what is due for inclusion or
not by querying mantis.

I just went to squeak.org and followed community links and I can find no
reference to Bob.  The things I want to be able to see and find easily are

1. sample images
2. list of packages loaded in the image
3. test results (name of class, number of green, yellow and red tests, and
if possible the assertion that failed or the error message for each yellow
and red test).

How do I get at this kind of info?  If I can't get at this then Bob is an
abstraction I don't understand and can't trust.  If it is manifested then it
needs to be findable easily from squeak.org.

Now if certain members of the board would volunteer to contribute to the

process, rather than replacing it without discussion, we would all be a
lot better of.

best regards

Keith

best
Eliot

Eliot Miranda wrote:
> Hi Keith,
>
> On Thu, Jul 2, 2009 at 4:20 AM, Keith Hodges <[hidden email]

> <mailto:[hidden email]>> wrote:
>
>     The existing community development model works fine enough.
>
>     1. Submit changes as change sets to mantis.
>
>     2. Bob builds and tests the changes in a basic image, a dev image
>     and a
>     full image
>
>     While you need your changes, and await the release with your fixes
>     integrated into it, you can load them manually from Mantis.
>
>     3. When Bob builds the new release he automatically loads changesets
>     from mantis, and fills in the MC repositories together with commit
>     messages.
>
>     The result is an image that looks as though it has been managed
>     with MC,
>     but the work is submitted in changesets that we all prefer.
>
>     This is an open process, and you can see what is due for inclusion or
>     not by querying mantis.
>
>

> I just went to squeak.org <http://squeak.org> and followed community

> links and I can find no reference to Bob.  The things I want to be
> able to see and find easily are
>
> 1. sample images

On their way.... see ftp.squeak.org/3.11 for some initial examples where
bob is building the LPF image

> 2. list of packages loaded in the image

This can be be included in the metafile that accompanies every build.
Images also contain documentation of the bug fixes that have been loaded.

> 3. test results (name of class, number of green, yellow and red tests,
> and if possible the assertion that failed or the error message for
> each yellow and red test).

Sure... the results from TestReporter do that. I am working on it. I did
have some icons that you can add to apache to give you the colors.

> How do I get at this kind of info?  If I can't get at this then Bob is
> an abstraction I don't understand and can't trust.  If it is
> manifested then it needs to be findable easily from squeak.org

> <http://squeak.org>.
This info will be available wherever bob is running, bob is supposed be
runnable in a distributed fashion, some results are being synced up to
ftp.squeak.org however you can see my bob server at
ftp://squeak:viewpoints@.../bob/output

Keith

> This domain name, "warwick.st", may still be available for registration!
>

Indeed, the nic.st failed to send out any reminders, so they expired my
domain without telling me.

Unfortunately at present I cant afford to re-register it.

Keith

On Thu, Jul 2, 2009 at 11:22 AM, Keith Hodges <[hidden email]> wrote:

> This domain name, "warwick.st", may still be available for registration!
>

Indeed, the nic.st failed to send out any reminders, so they expired my
domain without telling me.

Unfortunately at present I cant afford to re-register it.

How much does, say, a 2 year registration cost?   Does e.g. the board have that kind of ready cash?

Keith