On 26.01.2013, at 04:58, Yanni Chiu <yanni at rogers.com> wrote:

> On 25/01/13 1:48 PM, H. Hirzel wrote:
>> 
>> So this might be a good opportunity to start building another
>> distribution/release with what Frank proposes. So besides the current
>> one at http://www.squeakci.org/job/ReleaseSqueakTrunk/ we would have a
>>  "developer's release' with additional packages....
> 
> +1/-1
> 
> Don't forget the Pharo experience. There used to be a Pharo-Core-1.3 and Pharo-1.3 (a.k.a. Pharo-dev).
> 
> There was a ton of confusion when people reported a bug in "Pharo" - sometimes that meant Core, sometimes not.
> 
> With Pharo-1.4, the distinction between Core and non-Core was abandoned. IIUC, the reason was that developers worked day-to-day with the non-Core image - refactoring and so on - then had to make sure the changes worked in Core too. Going the other way, when working only in Core, if code is refactored or eliminated (because it looks like no senders in Core), then the problems would show up later when the non-Core image is built or run.


So what is their solution now?

- Bert -