ratliff.bobby at gmail.com
Tue Nov 5 09:44:27 EST 2013
Out of curiosity, how is the documentation usually bundled with a new
stable release into the pre-built binaries? Do you just use the latest
revision from the gnucash-docs repository?
On 11/4/2013 3:34 PM, Geert Janssens wrote:
> With 2.5.7 out of the door, I would like to look ahead at 2.6.
> I have just gone through the open bugs targeting the 2.6 milestone and
> reduced the set from 21 to 14. Some of the bugs I removed were actually
> bugs against register2 which is not a feature for 2.6 any more. Some
> need more info before we can decide (now marked as NEEDINFO).
> Are these bugs the remaining issues for 2.6 or is someone still working
> on something that should get included ?
> In these bugs I don't see anything that would still introduce major
> translation changes.
> There may be one translation issue left though: normally the gsettings
> schemas are translatable, but they currently aren't properly marked for
> translation. If I do that, this will include lots of translatable
> strings. Most of them were already in the gconf schema, so ideally most
> translations will simply be reused from before. I haven't tested this
> Question is: can we do a string freeze now, or should we wait for this
> to get fixed ?
> From earlier conversations, the last plan was to release 2.6 by the end
> of the year. Is this realistic ?
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
More information about the gnucash-devel