 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | You are not logged in.
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.
Offline
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.
Offline
Good idea. Let's try to hardproof this workflow and every term associated with it.
Offline
Using "fixed in release >= 1.4.2" should be enough? It will avoid you to edit the post again...
Offline
