[Sugar-devel] Are we ready for code freeze?

[Manuel Quiñones]

2013/9/2 Daniel Narvaez <dwnarvaez at gmail.com>:
> On 2 September 2013 21:00, Daniel Drake <dsd at laptop.org> wrote:
>>
>> On Mon, Sep 2, 2013 at 12:21 PM, Daniel Narvaez <dwnarvaez at gmail.com>
>> wrote:
>> > I propose we don't freeze and instead we keep releasing 0.99.x every
>> > four
>> > weeks, until we feel we have done enough testing and bug fixing. This is
>> > not
>> > what you are supposed to do with time based releases but I'd rather
>> > delay
>> > than release something we can't be proud of.
>>
>> Just as something to keep in mind, I would say that recent Sugar
>> release cycles have also had a certain amount of uncertainty around
>> this time. In previous cases we have just stuck to the timeline (more
>> or less) and released anyway, especially when it is unclear how long
>> the delay would otherwise need to be.
>
>
> That's good to know, thanks.
>
> Subjectively previous releases have not been of very good quality. And this
> one risks to be a lot worst because we don't have a team of several
> developers testing and fixing. The number of features we landed is probably
> greater than the number of fixes which can't be right, unless we are
> suddenly writing perfect code.
>
> I don't care too much about releasing or not, but IMO we should not go back
> accepting new features until the testing, triaging and bugs situation is a
> bit more under control.

I agree.  We should delay the hard freeze for 4 weeks and hope that by
that time we get some testing and bugfixing.

Development of sugar-web can continue as it is enough separated from
the other Sugar components.

-- 
.. manuq ..