Re: 2.4 release cycle

Tomas Frydrych wrote:
>
>
> This is to remind everyone that we agreed a hard feature freeze for
> April 15, so there really should not be any new features until the 2.4
> release.
>
> If we are to release 2.4 by the end of June, we need to start releasing
> pre-releases fairly soon so that we have enought feedback to iron out
> the problems. I suggest that we have a first pre-release by the end of
> the month, and we will take it from there (we should probably aim for a
> fortnightly releases, if that is workable). We should also start
> prioritizing bugs for 2.4 more consciously (and paying attention to the
> priorities).
>
> There will be some mismatch between the 2.4 aspirations and the reality,
> but there will be 2.6, etc. (For my part, both the Pango graphics and
> the Merge documents will not be ready for the release due to some
> unforeseen committments on my part, although I will continue working on
> the Pango time permitting.
>

Something I would like to push, and that is not intrusive, is the test
suite. It is not a useless effort and has been proven to be reallu
helpful in preventing regressions and testing code.

I'll try to put together more tests, and they are all outside the
current code, they should not influence, but for bugs to fix.

Doc is in the Wiki
http://www.abisource.com/twiki/bin/view/Abiword/TestingFramework

I'll update it.

Hub
Received on Tue Apr 19 22:35:43 2005