Feedback workflow  

This forum is dedicated to Autopano Pro / Giga bug reports and features discussion.
Please read the posting rules before starting a topic!
User avatar
AlexandreJ
Kolor Team
 
Topic author
Posts: 5969
Likes: 4 posts
Liked in: 2 posts
Joined: Mon Nov 14, 2005 4:56 pm
Location: Francin, France
Info

Feedback workflow

by AlexandreJ » Mon Mar 23, 2009 12:03 pm

22 October 2010 : Updated rules

The general way of working in this Bug report sub-forum is the following :
- We release an alpha / beta / version
- People that have found a bug can report it here ( please check that it has not been reported already )
- We read the thread. if we found nothing new, we'll acknowledge for that by saying ( issue open + number ).
If it has already been reported, we just make a link to the first reported URL.
This issue and it's number helps us to track that issue internally in our bug database.

After, that there is several possibilities :
- for real crash, we often have a high priority on these issues and they will be solved in next release.
- for medium and low priority issues, it depends on the date of release. It won't automatically happen on next release.

Just before a new release, every fixed issue gets a fixed posted in the topic.

User avatar
John_Sauter
Member
 
Posts: 173
Likes: 0 post
Liked in: 0 post
Joined: Sat Jul 28, 2007 4:59 pm
Location: New Hampshire, USA
Info

by John_Sauter » Mon Mar 23, 2009 12:59 pm

AlexandreJ wrote:The general way of working in this Bug report sub-forum is the following :
- We release an alpha / beta / version
- People that have found a bug can report it here
- We read the thread and try to reproduce the bug. If revelant, we open a bug case in our internal bug reporting tool ( it's then indicated in the thread )
- After it has been fixed, we'll write "Solved" or "fixed" or "improved" the thread.
- In the next release, the bug should then be fixed ( normally, you have to check that fact and report confirmed fixed in the thread ).
- When this bug reporting loop is finished, the thread is closed and moved to archive sub-forum.

People are finding your fourth step confusing. I recommend that you mark a bug that has been fixed internally as "solved in next release", or "fixed in next release" or "improved in next release". When the next release is made, go back and change "next release" to "current release" so those who suffered the problem are reminded to confirm and report.

User avatar
AlexandreJ
Kolor Team
 
Topic author
Posts: 5969
Likes: 4 posts
Liked in: 2 posts
Joined: Mon Nov 14, 2005 4:56 pm
Location: Francin, France
Info

by AlexandreJ » Mon Mar 23, 2009 1:24 pm

Good idea. Let's try to hardproof this workflow and every term associated with it.

User avatar
fma38
Member
 
Posts: 5840
Likes: 2 posts
Liked in: 0 post
Joined: Wed Dec 07, 2005 6:21 pm
Location: Grenoble, France
Info

by fma38 » Mon Mar 23, 2009 1:30 pm

Using "fixed in release >= 1.4.2" should be enough? It will avoid you to edit the post again...
Frédéric

Canon 20D + 17-40/f4 L USM + 70-200/f4 L USM + 50/f1.4 USM
Merlin/Orion panohead + Papywizard on Nokia N800 and HP TC-1100


Return to Autopano - Bugs & discussion

Who is online

Users browsing this forum: No registered users and 3 guests