[squeak-dev] 3.11 and the trunk

Igor Stasenko siguctua at gmail.com
Wed Aug 19 13:05:14 UTC 2009


It is clear that for different people, who get used to one or another tool,
sometimes, it is very hard to convince them to change their habits and
stop using old tool and start using a new one
immediately.
This is lenghtly process which could take years , and we should be patient.

I am understanding the 3.11 effort first, as a set of tools which has
to be written in order to simplify/automate
an image building process and also enable a more open, friendly
contribution process with less bottlenecks, with easily crossing fork
'barriers'.
So, i had never underestimated the value of such tools. But as i said,
it could take years before people take a full grasp of the idea. So,
patience, patience and patience.

Both 'trunk' and '3.11' depicting some kind of process.
And as Andreas stated, they are perpendicular in respect that they
having different targets/goals.
It may be hard to see, because both are about software development..
And i must say that 3.11 cares more about integration of already
existing artifact(s), not really matter what they are, while trunk
process is cares more about continuous development of a single
artifact (a Squeak release).

I am proposed already, to look for a ways, how Sake could help us in
developing a squeak release. I thought that it will be a first, little
baby-steps of all devs who involved currently in trunk to get
accustomed with new tool(s) , provided by Keith for us.
At first, i propose to write down a task for building/updating the
image from trunk , as an alternative to MCMUpdater.
I am really interesting in what places we could easily replace one
tool by another, but it is not really necessary to replace it, there
is _absolutely_ could be a cases where we could use both of them. Sake
is 'Make', which could use __any existing tool__ in order to build a
final artifact.
By writting down a set of automated, test-driven and repeatable tasks,
we will entering another dimension - where we could have a fully
automated build farm which doing nightly boring job for us. Hence the
Bob.

I seen a very good progress last couple of months around Squeak, since
we established a trunk process. And i am sure, more fun is waiting for
us over a next months, when we start using a new tools, such as
Bob/Sake, DeltaStreams and MC 1.6 / MC 2.0.


-- 
Best regards,
Igor Stasenko AKA sig.



More information about the Squeak-dev mailing list