On 03/14/2011 11:59 AM, Joao S. O. Bueno wrote:
> This decision, as I see it, change the release date from within
> "months" to within some weeks -
May I ask for the calculations that led you to the conclusion that we
are weeks away from a release? I haven't done the math yet, but I still
expect us to be months away from a release.
> I hope you have in mind that Translators have to know about so they
> can update translations as possible, as well. At some reasonable point
> before the release, a "string freeze" status for GIMPshould be set
> (even if a few string chanegs are to happen after that).
Thanks for the reminder. We should probably enter a soft string freeze
> Other than translation, we have to work the Python bindings so there
> are no functionality regressions, (whch includes the ability to work
> with layer groups) -
> so to the above list of bugs, we shuld at least have one more about this task.
> (this also depends on being able to transform layer groups).
Not including API to work with layer groups in Python is not a
regression, it's just missing functionality in one of the scripting
languages. It is unfortunate if GIMP 2.8 will be released without layer
groups support in Python, but the alternative is worse: not releasing
GIMP 2.8 at all. And we should arrange for the Python bindings to be
automatically generated from the PDB rather than wasting man-weeks on
manually keeping it up to date. Not an easy task perhaps, but the only
My GIMP Blog:
"Why GIMP 2.8 is not released yet"
Gimp-developer mailing list