Beta updates: 'changes' listing
Posted: Wed Sep 22, 2010 5:50 am
Hi Costas -
This question comes from now being able to see the changes of 'beta' in real time:
I think this has changed a situation.
Is it now valuable - to you - as well as us - to give us a (very short) comment or list of what is changed in a beta - so we know what to look for to use /or test?
I believe your last reply to this was 'No - this is a beta so... it is changeable - a fast update - - it could be deleted...' (I can't remember the thread).
But now with listing betas: new ones recognisable and old ones accessible - I think you have greater potential for feedback and involvement from your 'interested' users than ever before.
Maybe sometimes the change is not noticeable - - some pixels on a view - something not clear to describe and no feedback possible or wanted (I don't know...) - - then just make 'no comment' on a beta, as exampled below so we know you didn't just 'forget' or ignore... ( )
eg.
------
3.2.0.1109 -
'Search' /
Fast/ buttons, text entry
Detailed/ select bibles
------
3.3.0.1107 -
no comment
------
3.2.0.1106 -
--
---
3.2.0.1103 -
Bibles list: multi-select
----
If this is a .txt file included always in the .rar - it would be updateable with no filename change:
- make it cumulative
- just add at head of file each time the minimum info necessary:
- so the first entry is always the latest
Such a .txt file could also become the base for a 'changes in this version' to go with an official release.
I do understand this would take maybe one-two minutes to write - maybe those 2 mins will gain you feedback/testers to help? - - to make those two minutes valuable, and not lost time.
Example:
Tonight I find there are 3 updates since I last downloaded (1113: now 1116).
I installed 1116 and checked the area I am interested in and have a current thread on it of feedback:
(end of thread 'Multi-bible search, select 'button'' - with screenshots - http://forum.theword.gr/viewtopic.php?f=3&t=2411 )
- I did not see a change to that on a quick test.
I don't know what else is different: I cannot help test functions or give feedback -
And nor can anyone else....
- unless you have pm'd a person or it is in a thread I have not accessed...
So maybe you lose potential testers?....
The situation becomes more 'impossible to test/check' if there are now 10 - 15 - 20 betas since a person last downloads... But with a checklist they may now actually look at these features that otherwise they will not do.
If it doesn't work - and you find it wastes your time instead - then drop it again !
You may find it gives you more testers and useful feedback - or just more posts/pms /questions - that take time to answer, but no benefit to you...
So - how about trying it as an experiment?
miken
This question comes from now being able to see the changes of 'beta' in real time:
I think this has changed a situation.
Is it now valuable - to you - as well as us - to give us a (very short) comment or list of what is changed in a beta - so we know what to look for to use /or test?
I believe your last reply to this was 'No - this is a beta so... it is changeable - a fast update - - it could be deleted...' (I can't remember the thread).
But now with listing betas: new ones recognisable and old ones accessible - I think you have greater potential for feedback and involvement from your 'interested' users than ever before.
Maybe sometimes the change is not noticeable - - some pixels on a view - something not clear to describe and no feedback possible or wanted (I don't know...) - - then just make 'no comment' on a beta, as exampled below so we know you didn't just 'forget' or ignore... ( )
eg.
------
3.2.0.1109 -
'Search' /
Fast/ buttons, text entry
Detailed/ select bibles
------
3.3.0.1107 -
no comment
------
3.2.0.1106 -
--
---
3.2.0.1103 -
Bibles list: multi-select
----
If this is a .txt file included always in the .rar - it would be updateable with no filename change:
- make it cumulative
- just add at head of file each time the minimum info necessary:
- so the first entry is always the latest
Such a .txt file could also become the base for a 'changes in this version' to go with an official release.
I do understand this would take maybe one-two minutes to write - maybe those 2 mins will gain you feedback/testers to help? - - to make those two minutes valuable, and not lost time.
Example:
Tonight I find there are 3 updates since I last downloaded (1113: now 1116).
I installed 1116 and checked the area I am interested in and have a current thread on it of feedback:
(end of thread 'Multi-bible search, select 'button'' - with screenshots - http://forum.theword.gr/viewtopic.php?f=3&t=2411 )
- I did not see a change to that on a quick test.
I don't know what else is different: I cannot help test functions or give feedback -
And nor can anyone else....
- unless you have pm'd a person or it is in a thread I have not accessed...
So maybe you lose potential testers?....
The situation becomes more 'impossible to test/check' if there are now 10 - 15 - 20 betas since a person last downloads... But with a checklist they may now actually look at these features that otherwise they will not do.
If it doesn't work - and you find it wastes your time instead - then drop it again !
You may find it gives you more testers and useful feedback - or just more posts/pms /questions - that take time to answer, but no benefit to you...
So - how about trying it as an experiment?
miken