Hugin

Bug #679917 (sf-2781215)
Comment #10

Comment 10 for bug 679917

Revision history for this message

Yuv (yuv) wrote on 2010-11-30: Re: [Bug 679917] Re: Backup copy of project.

#10

On November 30, 2010 01:58:32 am rew wrote:
> If we drop all bug reports that are old this whole migration of bugs
> could've been prevented.

Would you volunteer to go through 400 tickets (bugs/features/patches) on the
old/slow SF infrastructure?

> Although I agree that formally "wishlist" is what you'd call a new
> feature like "autosave", it should be considered an essential fix to the
> system as long as sudden crashes still linger around.

I agree that it is an effective workaround. Not a fix. I prefer to see the
sudden crashes fixed and Hugin becoming more robust.

> A (hypothetical) bugfix ...

Not fix. Work around.

> I mentioned "nona" and the writing of the PTO file because it probably
> didn't crash until after I had once made a test-stitch. But in general
> I've had it crash before I've made my test-stitch as well.

The misunderstanding was all on our side. I apologize if it made you feel
that we do not consider your reports important enough.

To be totally explicit: I think the autosave feature request is a great idea
and should be on top of the list. But which list?

At SF we had three lists (bugs/patches/features). Bugs became irrelevant
because submerged by new reports. Features became irrelevant because ignored.
Patches was more or less under control, mainly because there were not that
many submissions.

Now we have a big combined list (around 400 tickets open at time of
migration), and an opportunity to do things well, i.e.
- first sort out what is feature request from what is bug report (there were a
lot of feature requests in the bug tracker)
- then go through them and prioritize them into a single "todo" list.

using the importance:
- feature requests -> wishlisth
- bug reports -> low/medium/high

then they can be mentally merged to a single todo-list again, trying to
balance between making the current software work as advertised (bug fixes) and
adding new features.

once we have sorted this mess, we can go more methodical about the todo-list
by using the Assigned-To and Milestone fileds.

Thank you for bearing with us and helping us sort the backlog
Yuv

On November 30, 2010 01:58:32 am rew wrote:
> If we drop all bug reports that are old this whole migration of bugs
> could've been prevented.

Would you volunteer to go through 400 tickets (bugs/features/patches) on the 
old/slow SF infrastructure?

> Although I agree that formally "wishlist" is what you'd call a new
> feature like "autosave", it should be considered an essential fix to the
> system as long as sudden crashes still linger around.

I agree that it is an effective workaround.  Not a fix.  I prefer to see the 
sudden crashes fixed and Hugin becoming more robust.

> A (hypothetical) bugfix ...

Not fix.  Work around.

The misunderstanding was all on our side.  I apologize if it made you feel 
that we do not consider your reports important enough.

To be totally explicit:  I think the autosave feature request is a great idea 
and should be on top of the list.  But which list?

At SF we had three lists (bugs/patches/features).  Bugs became irrelevant 
because submerged by new reports.  Features became irrelevant because ignored.  
Patches was more or less under control, mainly because there were not that 
many submissions.

Now we have a big combined list (around 400 tickets open at time of 
migration), and an opportunity to do things well, i.e.
- first sort out what is feature request from what is bug report (there were a 
lot of feature requests in the bug tracker)
- then go through them and prioritize them into a single "todo" list.

using the importance:
- feature requests -> wishlisth
- bug reports -> low/medium/high

then they can be mentally merged to a single todo-list again, trying to 
balance between making the current software work as advertised (bug fixes) and 
adding new features.

once we have sorted this mess, we can go more methodical about the todo-list 
by using the Assigned-To and Milestone fileds.

Thank you for bearing with us and helping us sort the backlog
Yuv