RSS/Atom feed Twitter
Site is read-only, email is disabled

preparing the 2.0.1 release

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

preparing the 2.0.1 release Sven Neumann 05 Apr 01:44
  preparing the 2.0.1 release Sven Neumann 05 Apr 02:22
  preparing the 2.0.1 release Tim Mooney 05 Apr 04:55
  preparing the 2.0.1 release Dave Neary 05 Apr 10:26
Sven Neumann
2004-04-05 01:44:59 UTC (about 20 years ago)

preparing the 2.0.1 release

Hi,

we said two weeks for 2.0.1, so that'd be this tuesday. Some time has been spent on the 2.0.1 bug list this weekend but still there's quite a list. Here's a summary with some comments. As usual the comments are just my opinion and I added them to ask you add yours, to object or to make you send patches.

#85103 Tools GIMP should warn user if extremely large fonts are requested - can be bumped to 2.0.2

#91384 General unaligned access when displaying an image - needs info

#93806 Script-Fu Script-Fu args parsing needs to be made sane - should be bumped to 2.2

#93856 Plugins IIR and RLE Blur blur inconsistently - has a patch that should be applied

#115774 General Tablet pointer becames core pointer - noone seems to have a clue what's going on, so bump it to 2.0.2

#120490 Tools Scale tool produces wrong output (misses parts of image) - can be bumped to 2.0.2

#121871 Plugins Saving large PSD's make the psd plugin crash. - can be bumped to 2.0.2

#123888 Plugins PSD images gets wrong "modulo" - can be bumped to 2.0.2

#128594 Tools Rotating layer more wide than 16000 pixels causes problem... - can be bumped to 2.0.2

#132366 General crashes when loading ( finding font ) - this one is fixed (workaround in gimp, real fix in freetype) and is only kept open to give people a chance to find the bug before filing yet another duplicate

#133719 User Interface crashes on paste
- eeky but unlikely to trigger, could be bumped to 2.0.2

#136219 Tools crash with shapeburst gradients (adaptive supersampling /... - the crash is fixed, but there is a claim that there could be a better fix; should be closed as FIXED

#136556 Tools Crop Tool Behaves Strangely
- would be nice to figure out what's going wrong, otherwise bump to 2.0.2

#136713 Plugins Select contiguous region in imagemap not fully functional... - not severe, up to Maurits what to do but it won't block the release

#138103 General unable to begin selection from absolute lower right hand ... - would have to take a closer look before I can express an opinion on this one

#138201 General
gimp 2.x mmx problem ?
- seems to be related to the compiler and the compiler options, can be bumped to 2.0.2

#138237 Tools Selection dragbox doesn't always reliably indicate final ... - there's a patch ready to be committed

#138238 Plugins jpeg plug-in crashes when opening file - seems to be a DLL hell problem or incompatible library versions; probably not a GIMP problem, can be bumped to 2.0.2

#138356 General Gimp 2.0 crashes on Image Scale - bad bug, has a stack trace and a simple patch that gives some insight but needs more review and testing

#138662 Script-Fu Copy Visible fails when layer mask active - there's a suggested workaround, needs to be looked at

#138714 Gimp-Python 3 Blind Mice...Sorry..3 bugs in Py-Slice - has a patch; Yosh seems to be on it

#138754 General path_get_point_at_dist() is unimplemented - seems to be less trivial then we believed initially; should be bumped before we do anything stupid

#138788 Plugins problems with Lighting Effects plug-in - has a patch that looks good

So, this is a good bunch of work. I'd really like to do 2.0.1 this tuesday, but it will need a few people helping, otherwise it will take a little longer.

Sven

Sven Neumann
2004-04-05 02:22:05 UTC (about 20 years ago)

preparing the 2.0.1 release

Hi,

perhaps I should also list the good news:

Bugs fixed since GIMP 2.0.0 ===========================
- don't leak file descriptor for the POSIX shm implementation (Yosh) - fixed path tool undo (#138086, Mitch) - don't transform drawables away (#138117, Mitch) - fixed issues with guillotine plug-in (#138314, Joao, Mitch) - fixed Slide script-fu (#138310, Nils Philippsen) - don't allow removed items to be accessed thru the PDB (#138311, Mitch) - skip fonts with invalid names (workaround for #132366, Sven) - fixed Spinning Globe script-fu (#138253, Sven) - fixed a bug in the IFSCompose plug-in (#138212, David Necas) - fixed undo corruption with floating selections (Pedro, Mitch) - fixed gimprc man-page (Sven)
- align JPEG setjump buffer on 16-byte boundary for ia64 (#138357, Yosh) - fixed Alien Glow Arrow script-fu (#138524, Sven) - fixed code that suppresses the transform tool grid (Simon) - push an undo for changing the text layer modification flag (#137767, Mitch) - make the user installation work with pixmap themes (#138379, Sven) - register .jpe as extension for JPEG images (#138776, Bolsh) - fixed issues with the Lighting Effects plug-in (#138788, William Skaggs) - don't crash on color corrections on empty selections (#138973, Sven) - made gimptool-2.0 create missing directories (#138980, Yosh) - made undo names translatable (#139000, Sven) - optimized grid drawing (#138081, Sven) - don't create a gimptool link to gimptool-2.0 (#139024, Sven)

Sven

Tim Mooney
2004-04-05 04:55:45 UTC (about 20 years ago)

preparing the 2.0.1 release

In regard to: [Gimp-developer] preparing the 2.0.1 release, Sven Neumann...:

#91384 General
unaligned access when displaying an image - needs info

I've added some comments on this one that will hopefully help the original poster provide more info, and/or verify whether this is still happening.

Tim

Dave Neary
2004-04-05 10:26:53 UTC (about 20 years ago)

preparing the 2.0.1 release

Hi all,

Sven Neumann wrote:

we said two weeks for 2.0.1, so that'd be this tuesday. Some time has been spent on the 2.0.1 bug list this weekend but still there's quite a list.

I just created the 2.0.2 milestone in Bugzilla.

I think that we should start thinking about ways to tidy up bugzilla somehow - in theory we should only have 2 or 3 active milestones (2.0.x, 2.2, Future, say) and we should be getting rid of a bunch of older 1.3.x releases, if possible. We currently have over 30 versions and 10 milestones which is making bug entry more complicated than it has to be.

I agree that all the bugs you suggest bumping should be bumped. Getting the bug fixes we have already done out there is more important.

Cheers, Dave.