Re: 3.0 Release plans

This sounds like a good plan. It would be nice to fix two build issues
on windows (bugs 13030 and 13389) before the official 3.0 release. Are
there any GSOC candidates willing to work on these bugs?

Also, can we close the following three bugs (included in meta-bug 13260):
bug 13226 - Fixed in rev. 30864?
bug 13238 - I cannot reproduce this bug on Ubuntu 1204.
bug 13251 - There is no file attached to the bug.

Simon

On Thu, Apr 11, 2013 at 10:38 PM, Hubert Figuière <[email protected]> wrote:
>
> Hi,
>
> That would be great to release AbiWord 3.0 soon.
>
> Here is the plan.
>
> Cut the abiword 3.0 branch ASAP. This will give us a baseline for the
> code. Use that to release 2.99 or 3.0 beta or something. Not sure yet
> how to call it.
>
> trunk will be open to new feature / development. More importantly it
> will be the basis of SoC.
>
> I'll see about cherry-picking bug fixes to 3.0 branch.
> There is a list of "outstanding bugs" for 3.0
>   http://bugzilla.abisource.com/show_bug.cgi?id=13260
> Not hard blocker, but wish list.
>
> The dialog soc 2012 branch: I had to revert the merge. I'd like to get
> this fixed for post 3.0 to have it in the next release.
>
> The Qt port: I have a bootstrap, I'd like to commit it to trunk as it
> cause some refactoring work at the same time. This would be used as a
> basis for the Qt port SoC *if* it happens (if SoC doesn't happen for
> that work could still go forward - there is a longer rationale to that).
>
> Cheers,
>
> Hub