[squeak-dev] Release engineering

Bert Freudenberg bert at freudenbergs.de
Fri Jul 17 17:45:12 UTC 2009


On 17.07.2009, at 19:38, Douglas Brebner wrote:

> Ian Trudel wrote:
>> 2009/7/17 Bert Freudenberg <bert at freudenbergs.de>:
>>
>>> In any case a process where development slows down when nearing a  
>>> release
>>> would be in order, we might need feature freezes etc. Maybe we  
>>> simply set a
>>> release date now and then work towards it?
>>>
>>
>> That would make sense. The trunk should be frozen at some point in  
>> the
>> perspective of a release and then enter in a release phase. And the
>> release phase can be something along 3.11 proposal. My idea of both
>> development process is that they are not mutually exclusive.
>>
>>
> Why not make a branch rather than freezing the trunk? That way it  
> should
> be easier to determine what goes into a release, especially if it's
> built from spec rather than hand crafted.

Given our rather small active developer community I do not find it  
advisable to split the work force. Everyone should work together  
towards a release and not just the few poor souls who work on the  
release branch. This way everyone uses the release candidate, it gets  
much wider testing etc.

I recently saw a presentation on the OpenBSD release process and found  
Theo's argument in favor of this convincing:
http://www.youtube.com/watch?v=i7pkyDUX5uM


- Bert -





More information about the Squeak-dev mailing list