I'm really concerned that 0.43 seems to be moving so slow. We don't have any real stoppers now, so why the delay? Let's do a pre2 now and aim for the release at the end of the week. What do you think?
Release mainatainers (Peter & Jon), if you don't have time to work on that (patches, pre2, final release), please report, so we can work around that. Overall I must say I'm rather disappointed by the performance of the release maintainers this time.
Unfortunately I can't now be on Jabber because I'm having Internet connection issues, but I'll do what I can to help push the release. I have about 120Kb of diffs in my local tree and I can't wait to merge them in. This "short release" seems to have consisted mostly of a very long freeze :(
Here are the most important outstanding issues:
- Several patches in the tracker. If any of these goes in, we need to do another pre with them. If not, we can release right away after pre1.
- Several tutorial translations in the tracker (Scislac, will you do this?)
- Screenshots:
-- Node editing by Scislac: almost there, waiting for a final version with more stuff
-- Connector tool by Alexandre Prokoudine: waiting for a combined shot with 2 diagrams and a blurb (if you can't do this, let me know and I'll post what I have)
-- Drawings with pressure sensitivity by Popolon - does anyone have contact info for him, as I haven't heard from him since he agreed to do this screenshot (more than a month ago)?
-- Anything else?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
bulia byak wrote:
- Several tutorial translations in the tracker (Scislac, will you do this?)
I'd be more than happy to, but I seem to have a problem. As you know, I can't do "make-all" on my system (for whatever reason). The problem that I run into is that if I do make-svg or make-html, it only generates English copies. Is there something I'm missing on how to generate the other languages tutorials? I will pull those out of the tracker as soon as I know how to do this.
- Screenshots:
-- Node editing by Scislac: almost there, waiting for a final version with more stuff
Yeah, just a few more additions that I will add this afternoon and it should be good to go.
And I definitely agree with your proposal for pre2 tonight and final by the end of the week... if this is what the fast releases will be like, lets please not do any more in the future. It gives false expectations.
-Josh
On 11/1/05, Joshua A. Andler <joshua@...533...> wrote:
bulia byak wrote:
- Several tutorial translations in the tracker (Scislac, will you do this?)
I'd be more than happy to, but I seem to have a problem. As you know, I can't do "make-all" on my system (for whatever reason). The problem that I run into is that if I do make-svg or make-html, it only generates English copies
The language is the last parameter in the command line, for example:
./make-svg basic /usr/share/saxon/lib/saxon.jar /usr/bin/inkscape es
will do Spanish.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Quoting bulia byak <buliabyak@...400...>:
I have about 120Kb of diffs in my local tree and I can't wait to merge them in.
This is what I'm most concerned about, actually; you and a number of other folks (e.g. rwst) have been forced to do a lot of parallel development without incremental merging (because CVS doesn't support it well).
We're going to have to be careful to avoid a train wreck when the tree reopens.
-mental
On 11/1/05, bulia byak <buliabyak@...400...> wrote:
- Several patches in the tracker. If any of these goes in, we need to
do another pre with them. If not, we can release right away after pre1.
- Several tutorial translations in the tracker (Scislac, will you do this?)
Another update of ru.po is still in the tracker.
-- Connector tool by Alexandre Prokoudine: waiting for a combined shot with 2 diagrams and a blurb (if you can't do this, let me know and I'll post what I have)
Well, _now_ I know your final decision on Connector screenshots :) Surely I can do that.
Alexandre
On 11/1/05, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On 11/1/05, bulia byak <buliabyak@...400...> wrote:
- Several patches in the tracker. If any of these goes in, we need to
do another pre with them. If not, we can release right away after pre1.
- Several tutorial translations in the tracker (Scislac, will you do this?)
Another update of ru.po is still in the tracker.
Yeah, I'll try to look through it tomorrow and commit.
-- Connector tool by Alexandre Prokoudine: waiting for a combined shot with 2 diagrams and a blurb (if you can't do this, let me know and I'll post what I have)
Well, _now_ I know your final decision on Connector screenshots :) Surely I can do that.
Sorry if I wasn't clear, that was my intention from the beginning. You just need to clearly explain in the blurb how you used - or did not use - the tool for making these drawings.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Tue, 1 Nov 2005, bulia byak wrote:
-- Connector tool by Alexandre Prokoudine: waiting for a combined shot with 2 diagrams and a blurb (if you can't do this, let me know and I'll post what I have)
Were these the ones that weren't really constructed using the connector tool? I remember some discussion about it while I was overseas but can't seem to find it in the archives.
If so, it would be good to have a screenshot built with the actual tool. Which I'm happy to do if Alexandre's ones don't cover this.
-- Anything else?
Only that we probably do need to have one more prerelease -- one that has Whiteboard support compiled in if we want to release with this.
Cheers, Michael
On 11/1/05, Michael Wybrow <mjwybrow@...1047...> wrote:
On Tue, 1 Nov 2005, bulia byak wrote:
-- Connector tool by Alexandre Prokoudine: waiting for a combined shot with 2 diagrams and a blurb (if you can't do this, let me know and I'll post what I have)
Were these the ones that weren't really constructed using the connector tool? I remember some discussion about it while I was overseas but can't seem to find it in the archives.
They did use the tool, but were tweaked later. I think it's still useful to have them, with an appropriate explanation. Another shot with pure connector-tool-only diagram will be nice too; anyone can submit it?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
One other thing we forgot to do (speaking of which... why don't we start a "Guide for Release Maintainers" wiki page?) is announce the prereleases on the site front page. This is important because this would bring us more testers. Can anyone please do this now? (Better late than never.)
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Tue, 2005-11-01 at 15:58 -0400, bulia byak wrote:
I'm really concerned that 0.43 seems to be moving so slow. We don't have any real stoppers now, so why the delay? Let's do a pre2 now and aim for the release at the end of the week. What do you think?
I'll do a pre2 tonight -- but I'm not sure all the patches are in for that release. Hopefully this should have all the whiteboard code in it, so the packages will all be correct.
--Ted
I've got one of the tests failing in distcheck... does anyone have a good guess on this one? Else I'll start investigating tomorrow.
--Ted
** (process:6780): WARNING **: Could not open units file '/home/ted/Development/inkscape.release/inkscape-0.42 +0.43pre2/_inst/share/inkscape/ui/units.txt': No such file or directory
** (process:6780): WARNING **: * INKSCAPE_DATADIR is: '/home/ted/Development/inkscape.release/inkscape-0.42 +0.43pre2/_inst/share'
** (process:6780): WARNING **: * INKSCAPE_UIDIR is: '/home/ted/Development/inkscape.release/inkscape-0.42 +0.43pre2/_inst/share/inkscape/ui'
Testing style... sp_style_new, sp_style_write_string...font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-indent:0;text-align:start;text-decoration:none;line-height:normal;letter-spacing:normal;word-spacing:normal;text-transform:none;direction:ltr;block-progression:tb;writing-mode:lr-tb;text-anchor:start;opacity:1;color:#000000;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;marker:none;marker-start:none;marker-mid:none;marker-end:none;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;visibility:visible;display:inline;overflow:visible;font-family:Bitstream Vera SansOK sp_style_merge_from_style_string(whitespace, ifset...OK sp_style_merge_from_style_string(whitespace, always...OK sp_style_merge_from_style_string("fill:", ifset)...OK sp_style_merge_from_style_string("font-family:", always)...OK sp_style_merge_from_style_string("fill: ", ifset)...OK sp_style_merge_from_style_string("font-family: ", always)...OK sp_style_merge_from_style_string(":none", ifset)...OK invalid color setting: #4321...OK invalid color setting: currentColor...OK invalid color setting: #87654321...OK invalid color setting: #42...OK invalid color setting: aquam...OK sp_style_merge_from_style_string(default): ifset...OK sp_style_merge_from_style_string(default): always...OK sp_style_merge_from_style_string...OK SP_SCALE24_MUL...OK sp_style_merge_from_dying_parent: opacity...Assertion `child.opacity.value == SP_SCALE24_FROM_FLOAT(cases[i].exp_float_val)' failed style: FAILED (17/18 tests passed) FAIL: style-test
On Tue, Nov 01, 2005 at 11:57:50PM -0800, Ted Gould wrote:
sp_style_merge_from_dying_parent: opacity...Assertion`child.opacity.value == SP_SCALE24_FROM_FLOAT(cases[i].exp_float_val)' failed style: FAILED (17/18 tests passed) FAIL: style-test
I'll have a look at this one. It doesn't fail for me, but I haven't yet tried with -O2; just compiling now.
pjrm.
On Thu, Nov 03, 2005 at 09:07:02AM +1100, Peter Moulder wrote:
On Tue, Nov 01, 2005 at 11:57:50PM -0800, Ted Gould wrote:
sp_style_merge_from_dying_parent: opacity...Assertion`child.opacity.value == SP_SCALE24_FROM_FLOAT(cases[i].exp_float_val)' failed style: FAILED (17/18 tests passed) FAIL: style-test
I'll have a look at this one. It doesn't fail for me, but I haven't yet tried with -O2; just compiling now.
Still no luck reproducing it here. I have now committed a change to show values of some relevant variables wenn the test fails, though.
Can someone cvs up, make check (or make style-test && ./style-test) and post the resulting test failure message?
Thanks,
pjrm.
You wrote
Still no luck reproducing it here. I have now committed a change to show values of some relevant variables wenn the test fails, though.
Can someone cvs up, make check (or make style-test && ./style-test) and post the resulting test failure message?
Testing style... sp_style_new, sp_style_write_string...font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-indent:0;text-align:start;text-decoration:none;line-height:normal;letter-spacing:normal;word-spacing:normal;text-transform:none;direction:ltr;block-progression:tb;writing-mode:lr-tb;text-anchor:start;opacity:1;color:#000000;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;marker:none;marker-start:none;marker-mid:none;marker-end:none;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;visibility:visible;display:inline;overflow:visible;font-family:Bitstream Vera SansOK sp_style_merge_from_style_string(whitespace, ifset...OK sp_style_merge_from_style_string(whitespace, always...OK sp_style_merge_from_style_string("fill:", ifset)...OK sp_style_merge_from_style_string("font-family:", always)...OK sp_style_merge_from_style_string("fill: ", ifset)...OK sp_style_merge_from_style_string("font-family: ", always)...OK sp_style_merge_from_style_string(":none", ifset)...OK invalid color setting: #4321...OK invalid color setting: currentColor...OK invalid color setting: #87654321...OK invalid color setting: #42...OK invalid color setting: aquam...OK sp_style_merge_from_style_string(default): ifset...OK sp_style_merge_from_style_string(default): always...OK sp_style_merge_from_style_string...OK SP_SCALE24_MUL...OK sp_style_merge_from_dying_parent: opacity...OK style: OK (all 18 passed)
ralf
On Thu, Nov 03, 2005 at 11:06:57AM +0100, Ralf Stephan wrote:
style: OK (all 18 passed)
Thanks. Apparently Ted was testing on a ppc machine. We tried to figure it out last night, but I'm still mystified.
Update: Have made some more progress today, with Michael's help.
Apparently there is a bug in gcc 4.0 on ppc with -O2: even a simple multiplication of `(double) 0xb28 * 0x66' (which should be exact even with float or unsigned arithmetic) gets the wrong answer.
More precisely:
$ (echo '#include <stdio.h>'; echo 'int main() { printf("%a\n", (double) 0xb28 * 0x66); }') > tst.c \ && gcc-4.0 -O2 tst.c && ./a.out 0x1.1c7c07d8802a6p+18
whereas using -O1 or -O0 gets the correct result of 0x1.1c7cp+18.
However, strangely, g++-4.0 -O2 does get the correct result on that machine. So I don't yet have a definitive answer why we get the wrong answer in style-test, but the bug in Apple's gcc-4.0 -O2 on Darwin/PPC, combined with the below analysis of what should happen, does give a reasonable indication that the style-test failure is caused by a compiler bug.
The remainder of this message was written before discovering this compiler bug. You can probably ignore it.
pjrm.
The calculations involved are as follows, I believe:
unsigned a = unsigned(0.7 * 0xff0000 + 0.5); unsigned b = unsigned(0.4 * 0xff0000 + 0.5); unsigned m = unsigned((double) a * b / 0xff0000 + .5)
where unsigned(expr + .5) is of course an idiom for rounding expr to an integer (assuming expr is in the range of unsigned, as is the case here).
0xff0000 is a multiple of ten, so I'd expect a and b to be calculated as exactly 0xff0000 * 7/10 or 4/10 (in exact arithmetic), even though 0.7 and 0.4 can't be exactly represented as a double. (Update: Michael's just confirmed that these are calculated exactly on his ppc machine.)
a and b are each less than 2**24, so their product in exact arithmetic would in 48 bits, so I'd expect (double) a * b to be calculated exactly assuming IEEE doubles with 53 bits of significand. (Casting has higher precedence than multiplication.)
The a * b / 0xff0000 in exact arithmetic is 0x476666.666... I'd have expected floating point to calculate it as 0x476666.66666668. Adding decimal 0.5 (0x0.8) gives 0x476666.e6666668. (My x86 box does indeed give this.)
Casting to unsigned should then give 0x476666.
On Tue, Nov 01, 2005 at 03:58:02PM -0400, bulia byak wrote:
-- Anything else?
(sorry I've been so absent... lots of stuff going on)
It looks like the dxf2svg converter has buffer overflows in it. Lots of them. Most of the code consists of static character buffers and strcat. :)
Since it doesn't really seem to be part of the build system, I just wanted to make sure no one added it suddenly. :)
participants (9)
-
unknown＠example.com -
Alexandre Prokoudine -
bulia byak -
Joshua A. Andler -
Kees Cook -
Michael Wybrow -
Peter Moulder -
Ralf Stephan -
Ted Gould