Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
On 14 Nov, Raphael Quinet wrote: Bugzilla is usually better at handling bugs than this mailing list: - Bugzilla is available to everybody, including those who do not read this list. I think that it was a mistake to send the 1.3.0 announcement to the gimp-user list (it should have been sent to this list only) but this is too late now and we should encourage everybody to use Bugzilla as a central place for bug reports, instead of forcing them to subscribe to this list or to browse through the archives of this list. Since this version is for developpers only it would be better to communicate over the mailinglists. I see bugzilla more as a longterm bugreporting mechanism. - You can also easily check the status of any bug report. As soon as you load the page for that bug, you can see if it has been fixed or not. If there is a lot of traffic on this list and you do not read it every day, then you may have to read a lot of mails before you know if a bug has already been fixed or not. I hope you considered that it's quite tricky for us to follow bugs in the stable versions since they're sometimes hard to reproduce. Now imagine myriads of bugreports for the (per definition) buggy developer version. We'll also have to measure them somehow and handle them you remember? :) I think that the best way to proceed now is to: - warn everybody (including on gimp-user and gimp-announce) that 1.3.0 is very unstable, is for developers only, and will be followed by 1.3.1 soon, - mention that 1.3.1 will not be announced on the users list, and - encourage everybody to check Bugzilla for the current status of the 1.3.x releases, and to report all bugs there. I'm still not convinced about the bugtracker usage here and this is also a matter of sven and mitch using it more actively than in the past because it's really hard to follow what's going on without having the insight of the resp. developer. Thusly I think it would be wise to give them a voice and respect their thoughts (though someone created the 1.3.0 version in bugzilla and this might have been Sven). -- Servus, Daniel ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
[EMAIL PROTECTED] writes: On 13 Nov, Michael Natterer wrote: Be afraid! It's shiny, it's new, it's unstable, it's b0rken, it's The GIMP 1.3 !! Get ready for reorganized, not-yet-really-working sourcecode, compile it, hack it, send patches and help making a new GIMP that kicks ass. Indeed. :) autoconf 2.52 chokes on the dnl'ed out perl-files in AC_OUTPUT in configure.in. Yeah, feels like we need a 1.3.1 pretty soon (which should be no problem now that lots of make dist issues are fixed). And I get this: /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/local/include -DGIMPDIR=\.gimp-1.3\ -DDATADIR=\/usr/local/share/gimp/1.3\ -DSYSCONFDIR=\/usr/local/etc/gimp/1.3\ -DG_LOG_DOMAIN=\LibGimpWidgets\ -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_DISABLE_COMPAT_H -DGTK_DISABLE_COMPAT_H -O2 -Wall -c gimpstock.c rm -f .libs/gimpstock.lo gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/local/include -DGIMPDIR=\.gimp-1.3\ -DDATADIR=\/usr/local/share/gimp/1.3\ -DSYSCONFDIR=\/usr/local/etc/gimp/1.3\ -DG_LOG_DOMAIN=\LibGimpWidgets\ -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_DISABLE_COMPAT_H -DGTK_DISABLE_COMPAT_H -O2 -Wall -Wp,-MD,.deps/gimpstock.pp -c gimpstock.c -fPIC -DPIC -o gimpstock.o gimpstock.c:183: `stock_menu_navigation' undeclared here (not in a function) gimpstock.c:183: initializer element is not constant gimpstock.c:183: (near initialization for `gimp_stock_menu_pixbufs[0].inline_data') gimpstock.c:184: `stock_menu_qmask_off' undeclared here (not in a function) gimpstock.c:184: initializer element is not constant gimpstock.c:184: (near initialization for `gimp_stock_menu_pixbufs[1].inline_data') gimpstock.c:185: `stock_menu_qmask_on' undeclared here (not in a function) gimpstock.c:185: initializer element is not constant gimpstock.c:185: (near initialization for `gimp_stock_menu_pixbufs[2].inline_data') That's indeed strange (but from time to time happens here too...). Just re-make, or if it's really evil, remove themes/Default/gimp-stock-pixbufs.h before. Guess the gdk-pixbuf stock header generation rules are somehow wrong... But apart from that it looks good. :) :) ciao, --Mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
Steinar H. Gunderson [EMAIL PROTECTED] writes: On Tue, Nov 13, 2001 at 02:32:08PM +0100, Michael Natterer wrote: Get ready for reorganized, not-yet-really-working sourcecode, compile it, hack it, send patches and help making a new GIMP that kicks ass. I do feel a bit stupid... But is the loading of _every_ file supposed to be broken? Or should I submit a proper bug report? ;-) Hi Steinar, please no bugreports yet for the 1.3 series, it's just too buggy -- we'd drown in reports :) loading files (in any format) works absolutely fine here. what kind of errors do you get? ciao, --Mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
(Should perhaps take this off the list?) On Tue, Nov 13, 2001 at 07:28:05PM +0100, Michael Natterer wrote: loading files (in any format) works absolutely fine here. what kind of errors do you get? I open a file (tested PNG, JPEG and BMP), and get the error Image resolution is out of bounds, using the default resolution instead. Then, a window that appears to be properly-sized (given the resolution in the image file) pops up, but instead of containing the image data it's just empty. Oh, I just found out what's going on -- the only layer in the picture suddenly has an opacity of 2%. If I open the Layers dialog and increase the opacity, the image appears to work as usual. /* Steinar */ -- Homepage: http://www.sesse.net/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
please no bugreports yet for the 1.3 series, it's just too buggy -- we'd drown in reports :) Mitch: Can you or Sven make a formal announcement to this effect to all relevant mailing lists and other places where this was announced? With the announce on users too, I fear you will soon have bug reports or people wanting to make bug reports. It would be nice to have a bug reports banned formal announce before people starting trying to make them. Especially if bugzilla doesn't have a GIMP 1.3 thing. I have this fear of people mistakenly submitting 1.3 bugs against 1.2 because 1.3 sin't there to choose. Thanks. bex ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
On Tue, 2001-11-13 at 23:23, [EMAIL PROTECTED] wrote: On 13 Nov, Rebecca J. Walter wrote: make them. Especially if bugzilla doesn't have a GIMP 1.3 thing. I have this fear of people mistakenly submitting 1.3 bugs against 1.2 because 1.3 sin't there to choose. FWIW there is a 1.3.0 target in bugzilla though I think it's not correct to have one. Having one is better than having people submit to 1.2 versions. Is there a way in bugzilla to have it there but have bug reports refused or an autoresponse that says bug reports are not accepted on that version right now? ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
On 13 Nov, Michael Natterer wrote: Yeah, feels like we need a 1.3.1 pretty soon (which should be no problem now that lots of make dist issues are fixed). Yes. That's indeed strange (but from time to time happens here too...). Just re-make, or if it's really evil, remove themes/Default/gimp-stock-pixbufs.h before. Guess the gdk-pixbuf stock header generation rules are somehow wrong... Seems like the clean target doesn't work. At least it didn't remove the file. From a quick glance at Makefile.am I couldn't see why -- Servus, Daniel ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 1.3.0
On 13 Nov, Rebecca J. Walter wrote: FWIW there is a 1.3.0 target in bugzilla though I think it's not correct to have one. Having one is better than having people submit to 1.2 versions. Is there a way in bugzilla to have it there but have bug reports refused or an autoresponse that says bug reports are not accepted on that version right now? I've no idea, but for now I changed the version tag to 1.3.0 - Development to emphasize the fact that this is work-in-progress. -- Servus, Daniel ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
