Re: Feature freeze still valid - Release plans

I agree with Hub's plan. Ideally, we should try to release version 3.0
early enough that it can be included in the Linux fall releases (late
September?)

Hub, when you write that non-regression bug fixes can be skipped for
3.0 release, do you mean that we should stop submitting such fixes for
now so that we do not accidentally break something or that we should
primarily work on fixing the bugs included in bug 13260?

Simon

On Fri, Aug 3, 2012 at 3:16 PM, Hubert Figuière <hfiguiere@teaser.fr> wrote:
>
> Hi all,
>
> A while ago we agreed on a feature freeze so that we could actually
> release AbiWord 3.0
>
> It seems that this has been ignored (yes looking at you Ingo).
>
> And this will apply to string freeze.
>
> Here is the idea:
>
> Release of 2.9.4 ASAP.
> Fix the various blocker bugs and regression, including Gtk3 that has
> some kinks
>
> Try to release 3.0 sometime soon, maybe with intermediate release. I
> propose to cut the 3.0 branch for a 2.99 release and use that. Which
> mean somebody will have to backport some fix or double commit.
>
> (ie we don't merge from 2.99 to trunk, and fixes for 2.99 are either
> ported to trunk or backported from trunk).
>
> Things that can be skipped for 3.0:
>
> -Mac port
> -Summer of Code
> -non regression bug fixes.
>
> Summmer of Code:
>
> The awesome work from our student isn't ignored. It will be merged to
> trunk AFTER the 3.0 branch is cut - conditional to not integration
> issues, of course. We can try to use that to release a 3.2 relatively
> quickly. Seems like a decent goal.
>
> Any idea, comments?
>
> Cheers,
>
> Hub
Received on Sat Aug 4 03:53:07 2012