Yearly seems a little slow, but might be about right to allow lots of time for testing. There will always be Jenkins for those who need a fix (sometimes guilty myself). Bug fix releases would be appreciated.
________________________________________ From: [email protected] [[email protected]] on behalf of Yanni Chiu [[email protected]] Sent: Friday, March 23, 2012 11:10 AM To: [email protected] Subject: Re: [Pharo-project] About 1.4 Release... On 23/03/12 5:34 AM, Marcus Denker wrote: > > Is that what we want? or will people say "without refactorings, I will not > use it?" I think the release needs to happen soon, so we can all have a new baseline. According to the Pharo consortium vision doc, the release plan (maybe not for 1.4, but in the future) is to become yearly with two bug fix releases. If this were in place, then "refactoring" would miss the boat. Is it a big enough item to delay a release? Personally, I use it if it's in the image, and miss it slightly if it's not there. That's because I often work on a stripped down image, so others may feel differently.
