[Cuis] Cuis base image reduced by 25%!

[Juan Vuletich]

On 29/06/2013 06:58 p.m., Frank Shearar wrote:
> ...
>> Well, maybe there's no need to provide the "none" image on each update, but
>> only on "official version release", if this concept still makes sense...
>> Thinking aloud now. I think that the Cuis-Smalltalk GitHub organization
>> could have 3 repositories:
>>
>>      Cuis-Smalltalk/Stable : Committed just a few times a year. Contains only
>> reasonable tested image(with packages), image(without any packages),
>> packages. Each commit is a Cuis version.revision number. All packages should
>> load and run reasonably well. If we're freezing a release, and some package
>> is not updated, and is incompatible with the release, it is removed from
>> here (i.e. it is "not supported" for this release).
>>
>>      Cuis-Smalltalk/Development : Contains more frequent commits of
>> image(with selected / all packages preloaded), supported packages (to ease
>> diffing in the web browser), and update stream (numbered change sets). Might
>> occasionally be broken, or include incomplete stuff. For people who want the
>> latest, and can cope with this. For example, package developers, and people
>> contributing code to the base image. Packages are only removed from here
>> when abandoned (i.e. they are broken/incompatible, and nobody is working on
>> fixing them anymore).
>>
>>      Cuis-Smalltalk/Historic : One zip file for each release
> Surely the natural approach to this in GitHub would be branches?
> "master" branch is your Stable, "devel" branch is your Development,
> and you fork off different branches for each release.
>
> frank

I guess you're right. I've never used branches, but it sounds like it 
makes sense to do as you say. Thanks.

Cheers,
Juan Vuletich