The path to FREEZE... Woohoo!
Hey all,
We're roughly 6 weeks behind the proposed schedule... not good, but could be worse. If we stick to it, things could shape up nicely.
A quick update... here is the one thing that MUST be done before moving to Freeze... posting of an "alpha" tarball.
The following outstanding issues HAVE to be addressed to not be cut (and most unfortunately have not been addressed fully during Frost): *Jon's swatches MUST be initially editable in the F&S dialog. *Jon's new Input Devices dialog needs whatever polish to be good enough (I saw regressions from 0.47 mentioned recently in the tracker). *Jon's "UX" work (specifically UI placement needs to be settled). *Tavmjong's LinuxFund text tool work (we'll take what we can get, great progress has been made!). *Felipe Sanches' color management work. The "not real" (device) cmyk thing MUST be addressed prior to release. I'm not saying to remove, but perhaps disable, it is a part of the SVG spec, but it's not how the CMYK workflow actually works.
Now is the time to bring up other possibly blocker bugs. Please speak up... things that can be fixed in point releases and that aren't critical/high priority should not be brought up.
Cheers, Josh
On May 13, 2010, at 3:55 AM, Joshua A. Andler wrote:
*Felipe Sanches' color management work. The "not real" (device) cmyk thing MUST be addressed prior to release. I'm not saying to remove, but perhaps disable, it is a part of the SVG spec, but it's not how the CMYK workflow actually works.
Well... it's not actually part of the spec yet, just proposed. The main problem there is that it is proposed for SVG 1.2, and is not a 1.1 feature.
The UI work is unfinished, but could be hooked to some other internal implementation. So I think disabling for now is good.
On 13/5/10 12:55, Joshua A. Andler wrote:
Now is the time to bring up other possibly blocker bugs. Please speak up... things that can be fixed in point releases and that aren't critical/high priority should not be brought up.
No blocker bugs found yet but here are two regressions that IMHO should be fixed for 0.48 ;)
Bug #583593 https://bugs.launchpad.net/inkscape/+bug/583593 “Regression: default styles for tools are not loaded for new users”
Bug #510618 https://bugs.launchpad.net/inkscape/+bug/510618 “Closing unchanged SVG asks for saving”
Both seem to be related to changes in 'src/widgets/toolbox.cpp'.
~suv
Hi,
Could all developers review their newly added strings? It would be nice if we could move to string freeze now so that translators have time to finish their work.
Regards. -- Nicolas
On Fri, 2010-05-21 at 07:24 +0000, Nicolas Dufour wrote:
Hi,
Could all developers review their newly added strings? It would be nice if we could move to string freeze now so that translators have time to finish their work.
I want to second this and emphasize the importance... we need to get strings frozen within the next 2 weeks (regardless of overall freeze status). If you know features will get finished up during freeze which don't have finalized strings yet, get the strings finalized even before the code. I don't want to burden our translators as it happened last time, and it will ensure we can streamline the release as much as possible.
Cheers, Josh
P.S. I am only giving 2 weeks for the string freeze to set to be friendly to our student developers.
participants (4)
-
Jon Cruz -
Joshua A. Andler -
Nicolas Dufour -
~suv