That is the road to never have a release.Looks like a lot of people are going to be running patched versions if the release goes without some enhancements.
It is easy. It is called pharo 3.1 or pharo 4.0. The rule is: Don�t change the current release being in freeze. Release it, change then everything you wanted in the next step and make sure you can release the next version pretty soon. IMHO the best solution to this kind of problems is to have small iterations.What about a ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedForSomeSurelyVeryValidReason ?(Let's make the name shorter but you get the idea).
On Fri, Mar 28, 2014 at 4:02 PM, Johan Brichau <johan@inceptive.be> wrote:Hi all,
With Sven's fixes loaded, our model unit tests are all running fine. The benchmarks indicate the same speed as in 1.4. This is really great!
I'm still running the entire suite of tests but that will take a while to complete. But essential datetime bugs should have been spotted already.
Great work Sven!
I think it's worth integrating. If not, we will definitely work with this patched version.
Johan
On 28 Mar 2014, at 13:36, Pharo4Stef <pharo4Stef@free.fr> wrote:
> Hi johan
>
> Please let us know because I would be in favor of integrating such speed up if your system fully work.
>
> stef
>
>
> On 28 Mar 2014, at 09:17, Johan Brichau <johan@inceptive.be> wrote:
>
>>
>> On 28 Mar 2014, at 06:24, Esteban Lorenzano <estebanlm@gmail.com> wrote:
>>
>>> Bugs are errors that prevents the system to run.
>>
>> <nagging>
>> Some performance problems make the system impossible to work with
>> </nagging>
>>
>> Anyway, going to check in Sven's changes today.
>>
>> cheers
>> Johan
>>
>
>