>  I am most curious about what will happen to 3.10 when 3.11 is released.
>
> Thanks,
> TimJ
Here is the theory!

In an LPF image:

Installer install: 'Tasks'.

The main workflow is summarized in the following releases generated by
the following classes/tasks which need to be fleshed out.

Squeak 3.11 Personal Test Candidate -
ReleaseAfterSqueak310Kph-#taskTESTCANDIDATE.
Squeak 3.11 Unstable T.C. -
ReleaseAfterSqueak310Unstable-#taskTESTCANDIDATE.
Squeak 3.11 Stable T.C. - ReleaseAfterSqueak310-#taskTESTCANDIDATE.
Squeak 3.11-basic Release Candidate -
ReleaseSqueak311-#taskRELEASECANDIDATE.
Squeak 3.11-basic Golden - ReleaseSqueak311-#taskGoGolden.

Derived images

Squeak-3.x-dev - Packages current load: 'Squeak-dev image'.  (czar:
damien, should already work in 3.9+)
Squeak-3.x-web - Packages current load: 'Squeak-web image'. (ditto)
Squeak-3.x-devbeta - Packages beta load: 'Squeak-dev image'. (ditto)
Squeak-3.x-webbeta - Packages beta load: 'Squeak-web image'. (ditto)
Squeak-3.x-fullbeta - Packages beta load: 'Squeak-full image'. (czar wanted)
Squeak-3.x-full - Packages current load: 'Squeak-full image'.
Squeak-3.x-max - Packages current load: 'Squeak-max image'. (czar wanted)
Squeak-3.x-fun  - tba (czar wanted)
Squeak-3.x(-*whatever*)-test  - Packages current load: 'AllTests'.
(loads tests into any image
Squeak-3.x-seaside  - Packages current load: 'Squeak-seaside image'.

Squeak 3.x-(*whatever*)-oneclick - ReleaseX-taskGenerateOneClick.
Squeak 3.11-minimal -  Release311-#taskMINIMAL
Squeak 3.11-kernel -  Release311-#taskKERNEL
Squeak 3.11.1-basic -  Release311-#taskUPDATE1
Squeak 3.11.2-basic -  Release311-#taskUPDATE2

So by extension, those who only want a minor update of the most
essentially essential fixes to 3.10 there is a set of tasks managed by
class ReleaseSqueak31-#taskUPDATE3
This would be applied via:

Installer install: 'Tasks'.
ReleaseSqueak310 taskUPDATE3103 run.
Packages current unload: 'Sake'. (to remove all vestiges of the
Sake/Tasks/Packages).

cheers

Keith