On Mon, Oct 8, 2012 at 2:29 AM, Inge Wallin <[email protected]> wrote:
> At 13th of April Boemann suggested an informal sprint to take care of the > bugs > in the calligracommons module since they "normally fall outside the itches > each of us like to scratch". > > To make a long story short, this sprint happened before the release of > Calligra 2.5 and it was a great success. More than 100 bugs were fixed and > Calligra was improved a lot in the process. > > Now I suggest that we do the same for 2.6 except we concentrate on > usability > problems, visual glitches and other misfeatures. In short: polish. > > I am tired of seeing reviews saying "Calligra has a great potential but is > unpolished". Let's take the step from potential to maturity! > > I suggest that we use the first week after 2.6beta and the branching, > which is > on Oct 26th. That means monday the 29th of October to sunday the 4th of > November. > > What do you say? > Good idea. I would also include crashes as first priority. Recent reviews showed several times that the applications crashed too often.
_______________________________________________ calligra-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/calligra-devel
