Translation policy

Christian Stimming christian at
Sat Jan 18 14:57:05 EST 2014

Am Dienstag, 14. Januar 2014, 13:42:13 schrieb John Ralls:
> > I've updated accordingly.
> > 
> > Also, as 2.6.0 is out the door, we are not in string freeze anymore. Just
> > commit whatever you think you'd like to do. (Yes, I know this has some
> > drawbacks as well, but a formal string freeze on the branch for the
> > releases really only makes sense if we have two branches, so that the
> > string-breaking patch can always go into the unstable branch. As we don't
> > have a separate unstable branch at this point in time, all patches can go
> > into "trunk".)
> No, all patches can not go into trunk/master. Bug fixes only until we branch
> 2.6. If you have some new feature that you just can’t wait to get started
> on, by all means get started, but do it in a branch in your own repository.

I was talking about translations. With respect to translations and user 
message changes, indeed all patches can go into trunk/master.

The question of new feature development is a different matter, though. 



> You can merge it into master after we branch 2.6. There are lots of bugs to
> work on, so work on them and commit the fixes to trunk.
> Regards,
> John Ralls

More information about the gnucash-devel mailing list