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
Received on Fri Apr 12 04:38:34 2013
This archive was generated by hypermail 2.1.8 : Fri Apr 12 2013 - 04:38:34 CEST