AbiWord Weekly News #56, (2001, week 32, released 2001.08.13)
Welcome to issue 56 of the AbiWord Weekly News.
This week AbiWord 0.9.1 was released, and we'll probably see a 0.9.2 early next week after some Windows build problems have been fixed.
No, 0.9.1 is not a brown paper bag release, but simply the result of the developers deciding to make very frequent releases in 0.9.x series until 1.0 is reached.
These 0.9.x releases, however, will not always be accompanied by binaries for all platforms. Of course, as more and more bugs get fixed during the 0.9.x cycle, we may see point-releases with accompanying binaries before 1.0.
Seeing as we're now in the 0.9.x cycle, I'd like to (yet again) ask people (users, developers, lurkers - the whole shebang) to go to the bug list in BugZilla and cast your votes for bugs you'd like to see fixed. The present list of priorities has not really changed for a long time (other than the bugs on it that have been nailed recently). This is your chance to voice your (personal) direction of the bug fixing effort! See below for details...
In this issue:
Editor(s) of this issue: Jesper Skov
Patch of the week goes to Jared Davis for his thesaurus work.
POW (Project Of the Week) and the new uPOW (User Project Of the Week) is an attempt at attracting new developers and entice help from users by lowering the bar of entry to doing something constructive for AbiWord. A POW will describe a goal and often outline how to get there.
Presently we have a few unclaimed POWs. Please see the POW status page for more details.
Here's the AbiWord bug update for the last week. If you can spare some time, please help us triage the bugs - you don't need to be able to program to do this.
These are the bug counts for the past 4 weeks:
Date: Submitted: QA: Open: ---------------------------------------------------- 2001.07.20 77 ( -10%) 87 ( -37%) 321 ( +3%) 2001.07.27 68 ( -11%) 108 ( +24%) 318 ( +0%) 2001.08.03 87 ( +27%) 118 ( +9%) 316 ( +0%) 2001.08.10 107 ( +22%) 133 ( +12%) 311 ( -1%)
As a user of AbiWord, you are able to vote on bugs you'd like to see closed. The process is quite simple:
You have 30 voting points you can cast in whatever proportions you'd like on anything between 1 and 30 bugs. But note that developers will likely prioritize a bug with 30 single votes than a bug with a single 30-unit vote. So vote with lower unit counts (5 or so) to make your voice heard!
From the sorted list of votes, we found the current Top 10 Bugs to be:
We have just started nominating bugs for the next two big releases. You, developer and user, can have your say on which bugs to nominate by casting your vote on bugs as described above. The current milestone distribution is as follows:
In the past week, the following 2 bugs have been closed (i.e., closed and verified fixed):1754 and 1825
Traffic on the developer mailing list has settled on about 200 postings per week.
This week, interesting topics on the developer list included:
Copyright 1998-2001 SourceGear Corporation, Sam
Tobin-Hochstadt and others. All rights reserved.
Send comments to firstname.lastname@example.org.
AbiSource, AbiSuite, AbiWord, and the AbiSource logo are trademarks of SourceGear Corporation. All other product names, company names, or logos cited herein are the property of their respective owners.