Hugin

Bug #679917 (sf-2781215)
Comment #6

Comment 6 for bug 679917

Revision history for this message

Yuv (yuv) wrote on 2010-11-29:

Dear Rogier,

I read again the whole bug report thread and I must say that I understand why Thomas misunderstood you. I would have too. Maybe it would have been politically safer to set the bug to incomplete and ask for clarification.

First, the initial report was from 0.7.0. Hugin has changed massively since. Thomas was not even around back then.

Second, I read in the initial report: "I'm most pissed that a pto file got saved to run "nona", but this gets (I think) cleaned up after running nona." Hugin does not save a pto file to run nona until the stitching process is started. Hence Thomas' assumption (and I would have assumed the same) that this happened while stitching, and that this was in hugin_stitch_project.

Now, one hour ago, comes more information. I agree with you that based on the new information this is more serious. However there are two (or three) parts to this ticket:
1. identify and prevent the crash in Hugin.
2. linder the consequences of hugin_stitch_project crashing by enabling the resuming of the stitch process with the makefile (Thomas' assumption)
3. add backup / auto-save functionality to Hugin (your feature request that would have prevented the crash from causing you serious loss)

1. would need to be "confirmed" and set to status "important".
2. & 3. would be "wishlist". Not because they are not important, but because strictly speaking they are new features and not fixes. At the moment we are trying to sort out through the large quantity of tickets outstanding from the migration and the distinction wishlist - not wishlist is to mark what is a feature request (adding new code) from what is a bug (error in existing code).

Please bear with us as we set these flags. They are not an expression of judgment on the importance of your ticket. They are just a way of categorizing the work that needs to be done and getting a clear overview of how much in the tracker is about existing features that need fixing and how much is about new features.

Dear Rogier,

I read again the whole bug report thread and I must say that I understand why Thomas misunderstood you.  I would have too.  Maybe it would have been politically safer to set the bug to incomplete and ask for clarification.

First, the initial report was from 0.7.0.  Hugin has changed massively since.  Thomas was not even around back then.

Second, I read in the initial report: "I'm most pissed that a pto file got saved to run "nona", but this gets (I think) cleaned up after running nona."  Hugin does not save a pto file to run nona until the stitching process is started.  Hence Thomas' assumption (and I would have assumed the same) that this happened while stitching, and that this was in hugin_stitch_project.

Now, one hour ago, comes more information.  I agree with you that based on the new information this is more serious.  However there are two (or three) parts to this ticket:
1. identify and prevent the crash in Hugin.
2. linder the consequences of hugin_stitch_project crashing by enabling the resuming of the stitch process with the makefile (Thomas' assumption)
3. add backup / auto-save functionality to Hugin (your feature request that would have prevented the crash from causing you serious loss)

1. would need to be "confirmed" and set to status "important".
2. & 3. would be "wishlist".  Not because they are not important, but because strictly speaking they are new features and not fixes.  At the moment we are trying to sort out through the large quantity of tickets outstanding from the migration and the distinction wishlist - not wishlist is to mark what is a feature request (adding new code) from what is a bug (error in existing code).

Please bear with us as we set these flags.  They are not an expression of judgment on the importance of your ticket.  They are just a way of categorizing the work that needs to be done and getting a clear overview of how much in the tracker is about existing features that need fixing and how much is about new features.