Looks like the freeze is going well, with nothing serious showing up. Is there anything preventing us from making a release, say, tomorrow?
Actually, Ted, since you are our Release Technician (right? :) what is the best time for you to cut the release?
Arpad, thanks for committing the translations. As for the assert, I think it's not very frequent, but its fix is likely to be too dangerous for so late in the freeze. I will fix it for the next version.
On Wed, 2004-07-14 at 15:23, bulia byak wrote:
Looks like the freeze is going well, with nothing serious showing up. Is there anything preventing us from making a release, say, tomorrow?
Not sure ... I'd like to get any remaining common warnings/assertions cleaned up (if the fixes are simple) so they don't annoy Windows users.
Also, the situation with "dead" formats in the Win32 file selector worries me. Has it been resolved?
Other than that it does look like we're done though.
Actually, Ted, since you are our Release Technician (right? :) what is the best time for you to cut the release?
This is probably a good time to review (and amend, if necessary) the release process as documented here:
http://www.inkscape.org/cgi-bin/wiki.pl?CreatingDists
Arpad, thanks for committing the translations. As for the assert, I think it's not very frequent, but its fix is likely to be too dangerous for so late in the freeze. I will fix it for the next version.
I found a simple workaround which I comitted.
-mental
On Wed, 14 Jul 2004, MenTaLguY wrote:
On Wed, 2004-07-14 at 15:23, bulia byak wrote:
Looks like the freeze is going well, with nothing serious showing up. Is there anything preventing us from making a release, say, tomorrow?
Not sure ... I'd like to get any remaining common warnings/assertions cleaned up (if the fixes are simple) so they don't annoy Windows users.
If it is simple to do, that might be worthwhile, but not if it'd hold up the release. For next release, it sounds like it would be very worthwhile to get these msgs redirected.
Other than that it does look like we're done though.
Cool! Congrats everyone.
Actually, Ted, since you are our Release Technician (right? :) what is the best time for you to cut the release?
This is probably a good time to review (and amend, if necessary) the release process as documented here:
Let's also make a big priority to get an OSX binary this time around; I was surprised we didn't have an OSX package for 0.38. Even if the package is not very good and performs poorly, it will be a start. :-)
Bryce
On Thu, Jul 15, 2004 at 12:35:57AM -0700, Bryce Harrington wrote:
Not sure ... I'd like to get any remaining common warnings/assertions cleaned up (if the fixes are simple) so they don't annoy Windows users.
If it is simple to do, that might be worthwhile, but not if it'd hold up the release. For next release, it sounds like it would be very worthwhile to get these msgs redirected.
I'm hesitant to sweep problems under the rug like this, and deprive us of notification of real bugs.
If we have problems of g_log being called (via g_error / g_return_if_fail etc.), then I'd consider doing work like propogating the requirements to callers and ensuring that there are no real problems.
I'm not too sure what these warning/assertion problems in question are though.
pjrm.
On Thu, 15 Jul 2004, Peter Moulder wrote:
On Thu, Jul 15, 2004 at 12:35:57AM -0700, Bryce Harrington wrote:
Not sure ... I'd like to get any remaining common warnings/assertions cleaned up (if the fixes are simple) so they don't annoy Windows users.
If it is simple to do, that might be worthwhile, but not if it'd hold up the release. For next release, it sounds like it would be very worthwhile to get these msgs redirected.
I'm hesitant to sweep problems under the rug like this, and deprive us of notification of real bugs.
If we have problems of g_log being called (via g_error / g_return_if_fail etc.), then I'd consider doing work like propogating the requirements to callers and ensuring that there are no real problems.
I'm not too sure what these warning/assertion problems in question are though.
The issue was simply that on Windows when one prints to the console, it causes a console window to pop up (God knows why) which looks woefully out of place and makes Inkscape look unprofessional. On Linux, it's moderately better - it throws the messages away.
The solution that I think would benefit us to adopt, would be to develop a redirection mechanism that allows these messages to be more usefully directed - to a place that does not cause annoyance but yet that is also possible to view and copy/paste into a bug report.
Bryce
El jue, 15-07-2004 a las 05:48, MenTaLguY escribió:
On Wed, 2004-07-14 at 15:23, bulia byak wrote:
Looks like the freeze is going well, with nothing serious showing up. Is there anything preventing us from making a release, say, tomorrow?
Not sure ... I'd like to get any remaining common warnings/assertions cleaned up (if the fixes are simple) so they don't annoy Windows users.
Also, the situation with "dead" formats in the Win32 file selector worries me. Has it been resolved?
Other than that it does look like we're done though.
Hi, I tried pre4 yesterday and found that the latest po I sent (last Tuesday) wasn't included. There are only 4 or 5 untranslated strings, nothing important, but I thought I'd mention it.
Great work, team. We've been mentioned on the spanish Slashdot, www.barrapunto.com, today because of the Openclipart initiative and I mentioned the upcoming 0.39 release.
Go, go..
Hi,
I tried pre4 yesterday and found that the latest po I sent (last Tuesday) wasn't included.
The latest version should be in CVS now, please check. http://cvs.sourceforge.net/viewcvs.py/inkscape/inkscape/po/es.po
(There was some confusion as to whether or not translations are affected by the hard freeze, that's why I have not committed earlier.)
Arpad Biro
__________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail
On Wed, 2004-07-14 at 20:48, MenTaLguY wrote:
Also, the situation with "dead" formats in the Win32 file selector worries me. Has it been resolved?
Here is a kind of hack for that:
https://sourceforge.net/tracker/index.php?func=detail&aid=991657&gro...
Basically it just doesn't create them to begin with, but does not list them and make them insensitive like in the GTK selector. (which I think is better).
I can't test this patch, so it may not even compile. If someone could look at it and see if it works that would be great.
--Ted
On Wed, 2004-07-14 at 12:23, bulia byak wrote:
Actually, Ted, since you are our Release Technician (right? :) what is the best time for you to cut the release?
I think I'll to with tarball king ;) Sounds a little bit seedier :)
Anyway, tonight would be fine, and Saturday night would be fine. Hopefully I won't fall asleep on the couch like I did last night ;)
--Ted
participants (8)
-
Arpad Biro -
Bryce Harrington -
bulia byak -
Jon A. Cruz -
Lucas Vieites -
MenTaLguY -
Peter Moulder -
Ted Gould